From: Christoph Lameter <clameter@engr.sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: steiner@sgi.com, linux-mm@kvack.org, alokk@calsoftinc.com
Subject: Re: [RFC] Make the slab allocator observe NUMA policies
Date: Tue, 15 Nov 2005 08:43:26 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.62.0511150841150.9258@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200511150434.15094.ak@suse.de>
On Tue, 15 Nov 2005, Andi Kleen wrote:
> On Monday 14 November 2005 20:08, Christoph Lameter wrote:
> > I have thought about various ways to modify kmem_getpages() but these do
> > not fit into the basic current concept of the slab allocator. The
> > proposed method is the cleanest approach that I can think of. I'd be glad
> > if you could come up with something different but AFAIK simply moving the
> > policy application down in the slab allocator does not work.
>
> I haven't checked all the details, but why can't it be done at the cache_grow
> layer? (that's already a slow path)
cache_grow is called only after the lists have been checked. Its the same
scenario as I described.
> If it's not possible to do it in the slow path I would say the design is
> incompatible with interleaving then. Better not do it then than doing it wrong.
If MPOL_INTERLEAVE is set then multiple kmalloc() invocations will
allocate each item round robin on each node. That is the intended function
of MPOL_INTERLEAVE right?
--
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:[~2005-11-15 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 22:04 Christoph Lameter
2005-11-11 3:06 ` Andi Kleen
2005-11-11 17:40 ` Christoph Lameter
2005-11-13 11:22 ` Andi Kleen
2005-11-14 18:05 ` Christoph Lameter
2005-11-14 18:44 ` Andi Kleen
2005-11-14 19:08 ` Christoph Lameter
2005-11-15 3:34 ` Andi Kleen
2005-11-15 16:43 ` Christoph Lameter [this message]
2005-11-15 16:51 ` Andi Kleen
2005-11-15 16:55 ` 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=Pine.LNX.4.62.0511150841150.9258@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=ak@suse.de \
--cc=alokk@calsoftinc.com \
--cc=linux-mm@kvack.org \
--cc=steiner@sgi.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