public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@in.ibm.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Reimplementation of linux dynamic percpu memory allocator
Date: Tue, 21 Dec 2004 00:55:58 +0530	[thread overview]
Message-ID: <20041220192558.GA17194@in.ibm.com> (raw)
In-Reply-To: <41C718C7.1020908@colorfullife.com>

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.

If there is a stress test I can use, I can try running it.

> >>>     
> >..
> For non-NUMA systems, I would use get_free_pages() to allocate a 
> multi-page area instead of map_vm_area(). Typically, get_free_pages() is 
> backed by large pte memory and map_vm_area() by normal virtual memory.

Hmm...the arithmetic becomes tricky then.  Right now I allocate
NR_CPUS * PCU_BLOCKSIZE + BLOCK_MANAGEMENT_SIZE amount of KVA for a block,
allocate pages for cpu_possible cpus and map corresponding va space
with allocated pages using map_vm_area.  We may fragment if
NR_CPUS * PCPU_BLOCKSIZE doesn't fit into a proper page order,
also we'd be wasting pages for !cpu_possible(cpus) of NR_CPUS

Thanks,
Kiran

  reply	other threads:[~2004-12-20 19:10 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 [this message]
2004-12-29 16:33       ` Manfred Spraul
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=20041220192558.GA17194@in.ibm.com \
    --to=kiran@in.ibm.com \
    --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