From: Christoph Lameter <christoph@lameter.com>
To: Anton Blanchard <anton@samba.org>
Cc: akpm@osdl.org, manfred@colorfullife.com, linux-kernel@vger.kernel.org
Subject: Re: slab not freeing with current -git
Date: Tue, 5 Jul 2005 18:27:11 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0507051822390.6516@graphe.net> (raw)
In-Reply-To: <20050706010450.GO12786@krispykreme>
On Wed, 6 Jul 2005, Anton Blanchard wrote:
>
> > That is the issue. It should fall back to kmalloc. One piece of the
> > patchset dropped out between Andrew and Linus.
>
> That helped, but I still had lots of free memory in the request_queue
> slab. Giving kmem_cache_alloc_node the same treatment fixed it, although
> I wonder if we just shouldnt be passing in -1.
No. No. -1 is the sign for undetermined that is also used in other pieces
of slab.c. Meaning do not do node specific allocs. The fix
should only modify kmem_cache_alloc_node. But we wont need that if the
new slab allocator would get in. Andrew?
Also if powerpc wants to use node specific allocations for block devices
then the powerpc arch needs to supply a pcibus_to_node function that does
return the correct node for the pcibus.
Index: linux-2.6.git/mm/slab.c
===================================================================
--- linux-2.6.git.orig/mm/slab.c 2005-07-05 17:03:30.000000000 -0700
+++ linux-2.6.git/mm/slab.c 2005-07-05 18:25:20.000000000 -0700
@@ -2372,6 +2372,9 @@
struct slab *slabp;
kmem_bufctl_t next;
+ if (nodeid == -1)
+ return kmem_cache_alloc_node(cachep, flags);
+
for (loop = 0;;loop++) {
struct list_head *q;
prev parent reply other threads:[~2005-07-06 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 22:45 Anton Blanchard
2005-07-05 22:51 ` Christoph Lameter
2005-07-05 22:59 ` Anton Blanchard
2005-07-05 23:33 ` Christoph Lameter
2005-07-05 23:55 ` Anton Blanchard
2005-07-06 0:05 ` Christoph Lameter
2005-07-06 1:04 ` Anton Blanchard
2005-07-06 1:27 ` Christoph Lameter [this message]
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.0507051822390.6516@graphe.net \
--to=christoph@lameter.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®