From: Manfred Spraul <manfred@colorfullife.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: lse-tech@lists.sourceforge.net, akpm@digeo.com, tomlins@cam.org,
"Kamble, Nitin A" <nitin.a.kamble@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATH] slab cleanup
Date: Mon, 30 Sep 2002 17:59:35 +0200 [thread overview]
Message-ID: <3D9874E7.70805@colorfullife.com> (raw)
In-Reply-To: 732392454.1033343702@[10.10.2.3]
Martin J. Bligh wrote:
>>Could someone test that it works on real SMP?
>
>
> Tested on 16-way NUMA-Q (shows up races quicker than anything ;-)).
> Boots, compiles the kernel 5 times OK. That's good enough for me.
> No performance regression, in fact was marginally faster (within
> experimental error though).
>
Thanks for the test. NUMA is on my TODO list, after figuring out
where/how to drain cpu caches and the free list.
I've found one stupid bug with debugging enabled: the new debug code
tries to poison NULL pointers, with limited success :-(
And one limitation might be important for arch specific code:
kmem_cache_create() during mem_init() is not possible anymore.
--
Manfred
WARNING: multiple messages have this Message-ID (diff)
From: Manfred Spraul <manfred@colorfullife.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: lse-tech@lists.sourceforge.net, akpm@digeo.com, tomlins@cam.org,
"Kamble, Nitin A" <nitin.a.kamble@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATH] slab cleanup
Date: Mon, 30 Sep 2002 17:59:35 +0200 [thread overview]
Message-ID: <3D9874E7.70805@colorfullife.com> (raw)
In-Reply-To: 732392454.1033343702@[10.10.2.3]
Martin J. Bligh wrote:
>>Could someone test that it works on real SMP?
>
>
> Tested on 16-way NUMA-Q (shows up races quicker than anything ;-)).
> Boots, compiles the kernel 5 times OK. That's good enough for me.
> No performance regression, in fact was marginally faster (within
> experimental error though).
>
Thanks for the test. NUMA is on my TODO list, after figuring out
where/how to drain cpu caches and the free list.
I've found one stupid bug with debugging enabled: the new debug code
tries to poison NULL pointers, with limited success :-(
And one limitation might be important for arch specific code:
kmem_cache_create() during mem_init() is not possible anymore.
--
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/
next prev parent reply other threads:[~2002-09-30 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 12:43 [PATH] slab cleanup Manfred Spraul
2002-09-29 13:56 ` Ed Tomlinson
2002-09-29 13:56 ` Ed Tomlinson
2002-09-30 6:55 ` Martin J. Bligh
2002-09-30 6:55 ` Martin J. Bligh
2002-09-30 15:59 ` Manfred Spraul [this message]
2002-09-30 15:59 ` Manfred Spraul
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=3D9874E7.70805@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--cc=nitin.a.kamble@intel.com \
--cc=tomlins@cam.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.