From: Andrew Morton <akpm@osdl•org>
To: Steven Rostedt <rostedt@goodmis•org>
Cc: linux-mips@linux-mips•org, davidm@hpl•hp.com,
linux-ia64@vger•kernel.org, mj@atrey•karlin.mff.cuni.cz,
spyro@f2s•com, joe@tensilica•com, ak@suse•de,
linuxppc-dev@ozlabs•org, paulus@samba•org,
benedict.gaster@superh•com, bjornw@axis•com, mingo@elte•hu,
grundler@parisc-linux•org, starvik@axis•com, torvalds@osdl•org,
tglx@linutronix•de, rth@twiddle•net, chris@zankel•net,
tony.luck@intel•com, linux-kernel@vger•kernel.org,
ralf@linux-mips•org, marc@tensilica•com, lethal@linux-sh•org,
schwidefsky@de•ibm.com, linux390@de•ibm.com, davem@davemloft•net,
parisc-linux@parisc-linux•org
Subject: Re: [PATCH 00/05] robust per_cpu allocation for modules
Date: Fri, 14 Apr 2006 15:06:25 -0700 [thread overview]
Message-ID: <20060414150625.3ba369d2.akpm@osdl.org> (raw)
In-Reply-To: <1145049535.1336.128.camel@localhost.localdomain>
Steven Rostedt <rostedt@goodmis•org> wrote:
>
> Example:
>
> DEFINE_PER_CPU(int, myint);
>
> would now create a variable called per_cpu_offset__myint in
> the .data.percpu_offset section.
Suppose two .c files each have
DEFINE_STATIC_PER_CPU(myint)
Do we end up with two per_cpu_offset__myint's in the same section?
next prev parent reply other threads:[~2006-04-14 22:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 21:18 [PATCH 00/05] robust per_cpu allocation for modules Steven Rostedt
2006-04-14 22:06 ` Andrew Morton [this message]
2006-04-14 22:12 ` Steven Rostedt
2006-04-14 22:12 ` Chen, Kenneth W
2006-04-15 3:10 ` [PATCH 00/08] robust per_cpu allocation for modules - V2 Steven Rostedt
2006-04-15 5:32 ` [PATCH 00/05] robust per_cpu allocation for modules Nick Piggin
2006-04-15 20:17 ` Steven Rostedt
2006-04-16 2:47 ` Nick Piggin
2006-04-16 3:53 ` Steven Rostedt
2006-04-16 7:02 ` Paul Mackerras
2006-04-16 13:40 ` Steven Rostedt
2006-04-16 14:03 ` Sam Ravnborg
2006-04-16 15:34 ` Arnd Bergmann
2006-04-16 18:03 ` Tony Luck
2006-04-17 0:45 ` Steven Rostedt
2006-04-17 2:07 ` Arnd Bergmann
2006-04-17 2:17 ` Steven Rostedt
2006-04-17 20:06 ` Ravikiran G Thirumalai
2006-04-17 6:47 ` Rusty Russell
2006-04-17 11:33 ` Steven Rostedt
2006-04-16 7:06 ` Nick Piggin
2006-04-16 16:06 ` Steven Rostedt
2006-04-17 17:10 ` Andi Kleen
2006-04-17 16:55 ` Christoph Lameter
2006-04-17 22:02 ` Ravikiran G Thirumalai
2006-04-17 23:44 ` Steven Rostedt
2006-04-17 23:48 ` Christoph Lameter
2006-04-18 1:51 ` Steven Rostedt
2006-04-18 6:42 ` Nick Piggin
2006-04-18 12:47 ` Steven Rostedt
2006-04-16 6:35 ` Paul Mackerras
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=20060414150625.3ba369d2.akpm@osdl.org \
--to=akpm@osdl$(echo .)org \
--cc=ak@suse$(echo .)de \
--cc=benedict.gaster@superh$(echo .)com \
--cc=bjornw@axis$(echo .)com \
--cc=chris@zankel$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=davidm@hpl$(echo .)hp.com \
--cc=grundler@parisc-linux$(echo .)org \
--cc=joe@tensilica$(echo .)com \
--cc=lethal@linux-sh$(echo .)org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mips@linux-mips$(echo .)org \
--cc=linux390@de$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=marc@tensilica$(echo .)com \
--cc=mingo@elte$(echo .)hu \
--cc=mj@atrey$(echo .)karlin.mff.cuni.cz \
--cc=parisc-linux@parisc-linux$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=ralf@linux-mips$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=rth@twiddle$(echo .)net \
--cc=schwidefsky@de$(echo .)ibm.com \
--cc=spyro@f2s$(echo .)com \
--cc=starvik@axis$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=tony.luck@intel$(echo .)com \
--cc=torvalds@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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