mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: christoph <christoph@scalex86.org>
Cc: ak@suse.de, linux-kernel@vger.kernel.org, shai@scalex86.org
Subject: Re: [PATCH] Move some variables into the "most_readonly" section??
Date: Tue, 14 Jun 2005 16:58:18 -0700	[thread overview]
Message-ID: <20050614165818.6f83fa6c.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0506141644160.4099@ScMPusgw>

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")));


generates this:

	.file	"t.c"
	.version	"01.01"
gcc2_compiled.:
.globl x
	.section	.data.mostly_readonly,"aw",@progbits
	.align 32
	.type	 x,@object
	.size	 x,4
x:
	.zero	4
	.ident	"GCC: (GNU) 2.96 20000731 (Red Hat Linux 7.3 2.96-113)"

Seems OK?

  reply	other threads:[~2005-06-14 23:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 19:58 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 [this message]
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

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=20050614165818.6f83fa6c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®