lkml.org 
[lkml]   [2006]   [Jun]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: remove __read_mostly?
On Sun, 25 Jun 2006, Arjan van de Ven wrote:

> On Sun, 2006-06-25 at 11:57 -0700, Andrew Morton wrote:
> > I'm thinking we should remove __read_mostly.
> >
> > Because if we use this everywhere where it's supposed to be used, we end up
> > with .bss and .data 100% populated with write-often variables, packed
> > closely together. The cachelines will really flying around.
>
>
> one thing we could/should do is have a "written during boot only"
> section; which we then can mark read only as well :)

To replicate an IRIX idea:

We could have section with variables that can only be modified by special
command. F.e.

enable_write_to_most_read_section()
<change variable>
disable_write_to_most_read_section()


This section could be a per cpu section that would be replicated
to all nodes on the system on disable_write_to_most_read_section().
That would mean that critical read only data would be node local.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-06-26 06:23    [W:0.116 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site