All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: christoph <christoph@scalex86.org>,
	ak@suse.de, linux-kernel@vger.kernel.org, shai@scalex86.org
Subject: Re: [PATCH] Move some variables into the "most_readonly" section??
Date: Wed, 15 Jun 2005 10:18:34 +1000	[thread overview]
Message-ID: <42AF73DA.6030601@yahoo.com.au> (raw)
In-Reply-To: <20050614165818.6f83fa6c.akpm@osdl.org>

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 

      parent reply	other threads:[~2005-06-15  0:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 19:58 [PATCH] Move some variables into the "most_readonly" section?? christoph
2005-06-08 13:18 ` Andi Kleen
2005-06-14 22:54   ` christoph
2005-06-14 23:04     ` Andi Kleen
2005-06-14 23:17       ` Christoph Lameter
2005-06-14 23:19         ` Andi Kleen
2005-06-14 23:27           ` Christoph Lameter
2005-06-14 23:54             ` Andi Kleen
2005-06-14 23:23     ` Andrew Morton
2005-06-14 23:46       ` christoph
2005-06-14 23:58         ` Andrew Morton
2005-06-15  0:05           ` christoph
2005-06-15  0:16             ` Andrew Morton
2005-06-15  0:41               ` Andi Kleen
2005-06-17 13:55                 ` Anton Blanchard
2005-06-27 23:17                   ` christoph
2005-06-15  0:18           ` Nick Piggin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42AF73DA.6030601@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=christoph@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shai@scalex86.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.