From: David Rientjes <rientjes@google.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-numa@vger.kernel.org,
Mel Gorman <mel@csn.ul.ie>,
Randy Dunlap <randy.dunlap@oracle.com>,
Nishanth Aravamudan <nacc@us.ibm.com>,
Adam Litke <agl@us.ibm.com>, Andy Whitcroft <apw@canonical.com>,
eric.whitney@hp.com, Lee Schermerhorn <lee.schermerhorn@hp.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [patch] nodemask: make NODEMASK_ALLOC more general
Date: Mon, 5 Oct 2009 20:46:12 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0910052036380.17606@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0910021839470.11884@gentwo.org>
On Fri, 2 Oct 2009, Christoph Lameter wrote:
> > NODEMASK_ALLOC(x, m) assumes x is a type of struct, which is unnecessary.
> > It's perfectly reasonable to use this macro to allocate a nodemask_t,
> > which is anonymous, either dynamically or on the stack depending on
> > NODES_SHIFT.
>
> There is currently only one user of NODEMASK_ALLOC which is
> NODEMASK_SCRATCH.
>
That changes with Lee's patchset for mempolicy hugepage allocations and
freeing, he'll be using it in generic hugetlb code.
> Can we generalize the functionality here? The macro is basically choosing
> between a slab allocation or a stack allocation depending on the
> configured system size.
>
> NUMA_COND__ALLOC(<type>, <min numa nodes for not using stack>,
> <variablename>)
>
> or so?
>
I assume we could, although it would be slightly messy because we'd be
coding a stack allocation in a macro when comparing the passed value
against CONFIG_NODES_SHIFT.
> Its likely that one way want to allocate other structures on the stack
> that may get too big if large systems need to be supported.
>
I don't think we currently have any examples of that other than
nodemask_t. We allocate arrays of length MAX_NUMNODES quite often for
things like node_to_cpumask_map, struct bootnode, etc, but no longer on
the stack even in NUMA emulation. I'd be interested to see any
non-nodemask use cases.
--
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>
next prev parent reply other threads:[~2009-10-06 3:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 16:57 [PATCH 0/10] hugetlb: V8 numa control of persistent huge pages alloc/free Lee Schermerhorn
2009-10-01 16:57 ` [PATCH 1/10] hugetlb: rework hstate_next_node_* functions Lee Schermerhorn
2009-10-01 16:57 ` [PATCH 2/10] hugetlb: add nodemask arg to huge page alloc, free and surplus adjust fcns Lee Schermerhorn
2009-10-01 16:58 ` [PATCH 3/10] hugetlb: factor init_nodemask_of_node Lee Schermerhorn
2009-10-02 9:48 ` Mel Gorman
2009-10-02 11:38 ` Lee Schermerhorn
2009-10-03 17:25 ` Andrew Morton
2009-10-01 16:58 ` [PATCH 4/10] hugetlb: derive huge pages nodes allowed from task mempolicy Lee Schermerhorn
2009-10-02 10:11 ` Mel Gorman
2009-10-02 22:41 ` David Rientjes
2009-10-02 22:16 ` [patch] nodemask: make NODEMASK_ALLOC more general David Rientjes
2009-10-02 22:48 ` Christoph Lameter
2009-10-03 1:03 ` KAMEZAWA Hiroyuki
2009-10-06 3:46 ` David Rientjes [this message]
2009-10-03 0:59 ` KAMEZAWA Hiroyuki
2009-10-02 22:16 ` [PATCH 4/10] hugetlb: derive huge pages nodes allowed from task mempolicy David Rientjes
2009-10-02 23:23 ` Christoph Lameter
2009-10-05 11:15 ` Lee Schermerhorn
2009-10-05 20:58 ` David Rientjes
2009-10-06 2:54 ` Lee Schermerhorn
2009-10-06 3:33 ` David Rientjes
2009-10-01 16:58 ` [PATCH 5/10] hugetlb: add generic definition of NUMA_NO_NODE Lee Schermerhorn
2009-10-01 16:58 ` [PATCH 6/10] hugetlb: add per node hstate attributes Lee Schermerhorn
2009-10-01 16:58 ` [PATCH 7/10] hugetlb: update hugetlb documentation for NUMA controls Lee Schermerhorn
2009-10-01 19:47 ` Randy Dunlap
2009-10-02 11:43 ` Lee Schermerhorn
2009-10-01 16:58 ` [PATCH 8/10] hugetlb: use only nodes with memory for huge pages Lee Schermerhorn
2009-10-01 16:59 ` [PATCH 9/10] hugetlb: handle memory hot-plug events Lee Schermerhorn
2009-10-01 16:59 ` [PATCH 10/10] hugetlb: offload per node attribute registrations Lee Schermerhorn
2010-03-31 11:23 ` [APPLIED] [PATCH 0/10] hugetlb: V8 numa control of persistent huge pages alloc/free Andy Whitcroft
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=alpine.DEB.1.00.0910052036380.17606@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=cl@linux-foundation.org \
--cc=eric.whitney@hp.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=linux-numa@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=nacc@us.ibm.com \
--cc=randy.dunlap@oracle.com \
/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