From: Arnd Bergmann <arnd@arndb.de>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, Mel Gorman <mel@csn.ul.ie>,
Christoph Lameter <clameter@sgi.com>,
Nick Piggin <npiggin@suse.de>,
David Rientjes <rientjes@google.com>,
eric.whitney@hp.com, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH/RFC 1/6] numa: Use Generic Per-cpu Variables for numa_node_id()
Date: Tue, 1 Dec 2009 00:43:35 +0100 [thread overview]
Message-ID: <200912010043.36115.arnd@arndb.de> (raw)
In-Reply-To: <1259612920.4663.156.camel@useless.americas.hpqcorp.net>
On Monday 30 November 2009, Lee Schermerhorn wrote:
> Looking at other asm/foo.h and asm-generic/foo.h relationships, I see
> that some define the generic version of the api in the asm-generic
> header if the arch asm header hasn't already defined it. asm/topology.h
> is an instance of this. It includes asm-generic/topology.h after
> defining arch specific versions of some of the api.
This works alright, but if you expect every architecture to include the
asm-generic version, you might just as well take that choice away from
the architecture and put the common code into the linux/foo.h file,
which you can still override with definitions in asm/foo.h.
Most of the asm-generic headers are just mostly generic, and get included
by some but not all architectures, the others defining the whole contents
of the asm-generic file themselves in a different way.
So if you e.g. want ia64 to do everything itself and all other architectures to
share some or all parts of asm-generic/topology, your approach is right,
otherwise just leave the code in some file in include/linux/.
Arnd <><
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, Mel Gorman <mel@csn.ul.ie>,
Christoph Lameter <clameter@sgi.com>,
Nick Piggin <npiggin@suse.de>,
David Rientjes <rientjes@google.com>,
eric.whitney@hp.com, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH/RFC 1/6] numa: Use Generic Per-cpu Variables for numa_node_id()
Date: Tue, 1 Dec 2009 00:43:35 +0100 [thread overview]
Message-ID: <200912010043.36115.arnd@arndb.de> (raw)
Message-ID: <20091130234335.vRzmOX-uOEXd0NGpQukHeFF3OntMHO2Sz0KtBIjAZRs@z> (raw)
In-Reply-To: <1259612920.4663.156.camel@useless.americas.hpqcorp.net>
On Monday 30 November 2009, Lee Schermerhorn wrote:
> Looking at other asm/foo.h and asm-generic/foo.h relationships, I see
> that some define the generic version of the api in the asm-generic
> header if the arch asm header hasn't already defined it. asm/topology.h
> is an instance of this. It includes asm-generic/topology.h after
> defining arch specific versions of some of the api.
This works alright, but if you expect every architecture to include the
asm-generic version, you might just as well take that choice away from
the architecture and put the common code into the linux/foo.h file,
which you can still override with definitions in asm/foo.h.
Most of the asm-generic headers are just mostly generic, and get included
by some but not all architectures, the others defining the whole contents
of the asm-generic file themselves in a different way.
So if you e.g. want ia64 to do everything itself and all other architectures to
share some or all parts of asm-generic/topology, your approach is right,
otherwise just leave the code in some file in include/linux/.
Arnd <><
next prev parent reply other threads:[~2009-11-30 23:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 21:17 [PATCH/RFC 0/6] Numa: Use Generic Per-cpu Variables for numa_*_id() Lee Schermerhorn
2009-11-13 21:17 ` Lee Schermerhorn
2009-11-13 21:17 ` [PATCH/RFC 1/6] numa: Use Generic Per-cpu Variables for numa_node_id() Lee Schermerhorn
2009-11-13 21:17 ` Lee Schermerhorn
2009-11-20 15:46 ` Christoph Lameter
2009-11-20 15:46 ` Christoph Lameter
2009-11-30 20:28 ` Lee Schermerhorn
2009-11-30 20:28 ` Lee Schermerhorn
2009-11-30 20:40 ` Matthew Wilcox
2009-11-30 20:40 ` Matthew Wilcox
2009-11-30 23:43 ` Arnd Bergmann [this message]
2009-11-30 23:43 ` Arnd Bergmann
2009-12-02 16:29 ` Lee Schermerhorn
2009-12-02 16:29 ` Lee Schermerhorn
2009-11-13 21:17 ` [PATCH/RFC 2/6] numa: x86_64: use generic percpu var numa_node_id() implementation Lee Schermerhorn
2009-11-13 21:17 ` Lee Schermerhorn
2009-11-20 15:48 ` Christoph Lameter
2009-11-20 15:48 ` Christoph Lameter
2009-11-13 21:18 ` [PATCH/RFC 3/6] numa: ia64: " Lee Schermerhorn
2009-11-13 21:18 ` Lee Schermerhorn
2009-11-20 15:50 ` Christoph Lameter
2009-11-20 15:50 ` Christoph Lameter
2009-11-13 21:18 ` [PATCH/RFC 4/6] numa: Introduce numa_mem_id()- effective local memory node id Lee Schermerhorn
2009-11-13 21:18 ` Lee Schermerhorn
2009-11-20 15:53 ` Christoph Lameter
2009-11-20 15:53 ` Christoph Lameter
2009-11-13 21:18 ` [PATCH/RFC 5/6] numa: ia64: support numa_mem_id() for memoryless nodes Lee Schermerhorn
2009-11-13 21:18 ` Lee Schermerhorn
2009-11-13 21:18 ` [PATCH/RFC 6/6] numa: slab: use numa_mem_id() for slab local memory node Lee Schermerhorn
2009-11-13 21:18 ` Lee Schermerhorn
2009-11-20 15:56 ` Christoph Lameter
2009-11-20 15:56 ` Christoph Lameter
2009-11-20 15:43 ` [PATCH/RFC 0/6] Numa: Use Generic Per-cpu Variables for numa_*_id() Christoph Lameter
2009-11-20 15:43 ` Christoph Lameter
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=200912010043.36115.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=eric.whitney@hp.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.de \
--cc=rientjes@google.com \
--cc=tj@kernel.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.