From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: linux-mm <linux-mm@kvack.org>, Nick Piggin <npiggin@suse.de>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@linux-foundation.org>,
Eric Whitney <eric.whitney@hp.com>
Subject: Re: [PATCH/RFC] slab: handle memoryless nodes efficiently
Date: Thu, 29 Oct 2009 15:18:59 -0400 [thread overview]
Message-ID: <1256843939.16599.71.camel@useless.americas.hpqcorp.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0910291728200.30007@V090114053VZO-1>
On Thu, 2009-10-29 at 17:30 -0400, Christoph Lameter wrote:
> Maybe better introduce an alternative to numa_node_id that refers to the
> next memory node?
>
> numa_mem_node_id?
>
> We can then use that in various subsystems and could use it consistently
> also in slab.c
Where should we put it? In page_alloc.c that manages the zonelists.
>
> One problem with such a scheme (and also this patch) is that multiple
> memory nodes may be at the same distance to a processor on a memoryless
> node. Should the allocation not take memory from any of these nodes?
Well, this is the case for normal page allocations as well, but we
choose one, in build_zonelists(), that we'll use whenever a page
allocation overflows the target node selected by the mempolicy. So,
that seemed a reasonable node to use for slab allocations.
Thoughts?
Lee
--
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-29 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 17:08 Lee Schermerhorn
2009-10-29 21:30 ` Christoph Lameter
2009-10-29 19:18 ` Lee Schermerhorn [this message]
2009-10-29 23:33 ` 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=1256843939.16599.71.camel@useless.americas.hpqcorp.net \
--to=lee.schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=eric.whitney@hp.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
/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