Re: [PATCH] Move some variables into the "most_readonly" section??

[Nick Piggin <nickpiggin@yahoo.com.au>]

Andrew Morton wrote:
> christoph <christoph@scalex86.org> wrote:
>
> > On Tue, 14 Jun 2005, Andrew Morton wrote:
> >
> >
> > > I think readmostliness and alignment are mostly-unrelated concepts and
> > > should have separate tag thingies.  IOW,
> > > __cacheline_aligned_mostly_readonly goes away and to handle things like the
> > > cpu maps we do:
> >
> > Yup that makes the whole thing much more sane. Can we specify multiple 
> > attributes to a variable?
>
>
> I suppose so.
>
> Compiling this:
>
> int x   __attribute__((__aligned__(32)))
>         __attribute__((__section__(".data.mostly_readonly")));

Can I just throw in something unrelated and not very constructive
and ask that we call it 'read_mostly' instead of mostly_readonly?

mostly_readonly kind of says to me that most items in the section
are read only, read_mostly says all the items are mostly only read.

--
SUSE Labs, Novell Inc.

Send instant messages to your online friends http://au.messenger.yahoo.com 
-
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/