From: Manfred Spraul <manfred@colorfullife.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Christoph Lameter <christoph@lameter.com>,
Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Fw: [PATCH] NUMA Slab Allocator
Date: Wed, 16 Mar 2005 20:09:18 +0100 [thread overview]
Message-ID: <4238845E.5060304@colorfullife.com> (raw)
In-Reply-To: <273220000.1110999247@[10.10.2.4]>
Martin J. Bligh wrote:
>That'd be my inclination .... but OTOH, we do that for pagecache OK.
>
The page cache doesn't have a global hash table.
> Dunno,
>I'm torn. Depends if there's locality on the file access or not, I guess.
>Is there any *harm* in doing it node local .... perhaps creating a node
>mem pressure imbalance (OTOH, there's loads of stuff that does that anyway ;-))
>
>
>
The harm is slower kmem_cache_free and a lower hit ratio for the per-cpu
caches: kmem_cache_free must identify and return wrong node objects, and
due to these returns, the per-cpu array is more often empty in
kmem_cache_alloc.
IIRC someone from SGI wrote that they have seen bad performance in
fork-bomb tests on large cpu count systems which might be caused by
inter-node traffic on the mm_struct structure and that they think that a
numa aware allocator would help. As far as I know no tests were done to
very that assumption.
--
Manfred
WARNING: multiple messages have this Message-ID (diff)
From: Manfred Spraul <manfred@colorfullife.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Christoph Lameter <christoph@lameter.com>,
Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Fw: [PATCH] NUMA Slab Allocator
Date: Wed, 16 Mar 2005 20:09:18 +0100 [thread overview]
Message-ID: <4238845E.5060304@colorfullife.com> (raw)
In-Reply-To: <273220000.1110999247@[10.10.2.4]>
Martin J. Bligh wrote:
>That'd be my inclination .... but OTOH, we do that for pagecache OK.
>
The page cache doesn't have a global hash table.
> Dunno,
>I'm torn. Depends if there's locality on the file access or not, I guess.
>Is there any *harm* in doing it node local .... perhaps creating a node
>mem pressure imbalance (OTOH, there's loads of stuff that does that anyway ;-))
>
>
>
The harm is slower kmem_cache_free and a lower hit ratio for the per-cpu
caches: kmem_cache_free must identify and return wrong node objects, and
due to these returns, the per-cpu array is more often empty in
kmem_cache_alloc.
IIRC someone from SGI wrote that they have seen bad performance in
fork-bomb tests on large cpu count systems which might be caused by
inter-node traffic on the mm_struct structure and that they think that a
numa aware allocator would help. As far as I know no tests were done to
very that assumption.
--
Manfred
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-03-16 19:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050315204110.6664771d.akpm@osdl.org>
2005-03-16 18:34 ` Fw: [PATCH] NUMA Slab Allocator Manfred Spraul
2005-03-16 18:34 ` Manfred Spraul
2005-03-16 18:54 ` Martin J. Bligh
2005-03-16 18:54 ` Martin J. Bligh
2005-03-16 19:09 ` Manfred Spraul [this message]
2005-03-16 19:09 ` Manfred Spraul
2005-03-30 5:30 ` API changes to the slab allocator for NUMA memory allocation Christoph Lameter
2005-03-30 5:30 ` Christoph Lameter
2005-03-30 5:30 ` Christoph Lameter
2005-03-30 5:56 ` Manfred Spraul
2005-03-30 5:56 ` Manfred Spraul
2005-03-30 5:56 ` Manfred Spraul
2005-03-30 15:55 ` Christoph Lameter
2005-03-30 15:55 ` Christoph Lameter
2005-03-30 15:55 ` Christoph Lameter
2005-03-30 17:55 ` Manfred Spraul
2005-03-30 17:55 ` Manfred Spraul
2005-03-30 18:13 ` Christoph Lameter
2005-03-30 18:13 ` Christoph Lameter
2005-03-30 18:13 ` 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=4238845E.5060304@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.