From: Badari Pulavarty <pbadari@us.ibm.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] reduce fragmentation due to kmem_cache_alloc_node
Date: 11 Oct 2004 10:12:24 -0700 [thread overview]
Message-ID: <1097514734.12861.366.camel@dyn318077bld.beaverton.ibm.com> (raw)
In-Reply-To: <41684BF3.5070108@colorfullife.com>
Manfred,
This patch seems to work fine on my AMD machine.
I tested your patch on 2.6.9-rc2-mm3.
It seemed to have fixed fragmentation problem I was
observing, but I don't think it fixed the problem
completely. I still see some fragmentation, with
repeated tests of scsi-debug, but it could be due
to the test. I will collect more numbers..
Thanks,
Badari
On Sat, 2004-10-09 at 13:37, Manfred Spraul wrote:
> Hi Andrew,
>
> attached is a patch that fixes the fragmentation that Badri noticed with
> kmem_cache_alloc_node. Could you add it to the mm tree? The patch is
> against 2.6.9-rc3-mm3.
>
> Description:
> kmem_cache_alloc_node tries to allocate memory from a given node. The
> current implementation contains two bugs:
> - the node aware code was used even for !CONFIG_NUMA systems. Fix:
> inline function that redefines kmem_cache_alloc_node as kmem_cache_alloc
> for !CONFIG_NUMA.
> - the code always allocated a new slab for each new allocation. This
> caused severe fragmentation. Fix: walk the slabp lists and search for a
> matching page instead of allocating a new page.
> - the patch also adds a new statistics field for node-local allocs. They
> should be rare - the codepath is quite slow, especially compared to the
> normal kmem_cache_alloc.
>
> Badri: Could you test it?
> Andrew, could you add the patch to the next -mm kernel? I'm running it
> right now, no obvious problems.
>
> Signed-Off-By: Manfred Spraul <manfred@colorfullife.com>
>
>
> ______________________________________________________________________
--
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:[~2004-10-11 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 20:37 Manfred Spraul
2004-10-11 17:12 ` Badari Pulavarty [this message]
2004-10-11 18:07 ` Manfred Spraul
2004-10-15 18:08 ` Badari Pulavarty
2004-10-15 22:33 ` Badari Pulavarty
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=1097514734.12861.366.camel@dyn318077bld.beaverton.ibm.com \
--to=pbadari@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.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