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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
