All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Badari Pulavarty <pbadari@us.ibm.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: Mon, 11 Oct 2004 20:07:10 +0200	[thread overview]
Message-ID: <416ACBCE.9090500@colorfullife.com> (raw)
In-Reply-To: <1097514734.12861.366.camel@dyn318077bld.beaverton.ibm.com>

Badari Pulavarty wrote:

>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..
>
>  
>
Did you disable the !CONFIG_NUMA block from <linux/slab.h> or leave it 
enabled? If the CONFIG_NUMA test is in the header file, then my patch is 
identical to you proposal, except that I've changed the global 
declaration instead of just the call from alloc_percpu.

--
    Manfred

WARNING: multiple messages have this Message-ID (diff)
From: Manfred Spraul <manfred@colorfullife.com>
To: Badari Pulavarty <pbadari@us.ibm.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: Mon, 11 Oct 2004 20:07:10 +0200	[thread overview]
Message-ID: <416ACBCE.9090500@colorfullife.com> (raw)
In-Reply-To: <1097514734.12861.366.camel@dyn318077bld.beaverton.ibm.com>

Badari Pulavarty wrote:

>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..
>
>  
>
Did you disable the !CONFIG_NUMA block from <linux/slab.h> or leave it 
enabled? If the CONFIG_NUMA test is in the header file, then my patch is 
identical to you proposal, except that I've changed the global 
declaration instead of just the call from alloc_percpu.

--
    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>

  reply	other threads:[~2004-10-11 18:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-09 20:37 [PATCH] reduce fragmentation due to kmem_cache_alloc_node Manfred Spraul
2004-10-11 17:12 ` Badari Pulavarty
2004-10-11 17:12   ` Badari Pulavarty
2004-10-11 18:07   ` Manfred Spraul [this message]
2004-10-11 18:07     ` Manfred Spraul
2004-10-15 18:08 ` Badari Pulavarty
2004-10-15 18:08   ` Badari Pulavarty
2004-10-15 22:33   ` 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=416ACBCE.9090500@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pbadari@us.ibm.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 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.