All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Ravikiran G Thirumalai <kiran@in.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Reimplementation of linux dynamic percpu memory allocator
Date: Wed, 29 Dec 2004 17:33:44 +0100	[thread overview]
Message-ID: <41D2DC68.5080805@colorfullife.com> (raw)
In-Reply-To: <20041220192558.GA17194@in.ibm.com>

Ravikiran G Thirumalai wrote:

>On Mon, Dec 20, 2004 at 07:24:07PM +0100, Manfred Spraul wrote:
>  
>
>>No, not fast path. But it can happen a few thousand times. The slab 
>>implementation failed due to heavy internal fragmentation. If your code 
>>runs fine with a few thousand users, then there shouldn't be a problem.
>>    
>>
>
>  
>
Could you ask Badari Pulavarty (pbadari@us.ibm.com)?
He noticed the fragmentation problem with the original 
kmem_cache_alloc_node implementation. Perhaps he could just run your 
version with his test setup:
The thread with the fix is at:

http://marc.theaimsgroup.com/?t=109735434400002&r=1&w=2

--
    Manfred

  reply	other threads:[~2004-12-29 16:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 22:29 [RFC] Reimplementation of linux dynamic percpu memory allocator Manfred Spraul
2004-12-20 18:20 ` Ravikiran G Thirumalai
2004-12-20 18:24   ` Manfred Spraul
2004-12-20 19:25     ` Ravikiran G Thirumalai
2004-12-29 16:33       ` Manfred Spraul [this message]
2004-12-29 17:52         ` Ravikiran G Thirumalai
2005-01-12 18:12         ` Ravikiran G Thirumalai
  -- strict thread matches above, loose matches on Subject: below --
2004-12-17 22:03 Ravikiran G Thirumalai

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=41D2DC68.5080805@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=kiran@in.ibm.com \
    --cc=linux-kernel@vger.kernel.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.