public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sven Krohlas <sven@asbest-online.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Understanding schedular and slab allocation
Date: Wed, 15 Dec 2004 17:14:28 +0100	[thread overview]
Message-ID: <41C062E4.3030906@asbest-online.de> (raw)
In-Reply-To: <3bGVh-1jR-23@gated-at.bofh.it>

Hi,

>> Btw: is anybody working on the slab allocator as described in Bonwicks
>> 2001 paper?
> Linux already fronts the slab allocator with per-cpu pools.

Well, I haven't had such a deep look at the 2001 version (my topic was
the current implementation)...
I've seen the per-cpu pools. Bonwick talks in his paper of allocations in
guaranteed constant time (using vmem). Is this goal already achived in
Linux? There is a lock protecting the cache_chain, doesn't this hurt
scalability?

And what about the other improvements?

-vmem for allocating general resources
-A user-space implementation (well I know, that's a bit off topic here..)

Are they already implemented/is anybody working on this or are there
already known better solutions than Bonwicks suggestions?

Greetings,
Sven

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3bGLs-1dr-3@gated-at.bofh.it>
     [not found] ` <3bGLs-1dr-1@gated-at.bofh.it>
     [not found]   ` <3bGVh-1jR-23@gated-at.bofh.it>
2004-12-15 16:14     ` Sven Krohlas [this message]
     [not found] <3byuD-2Z8-7@gated-at.bofh.it>
2004-12-15 12:40 ` Understanding schedular and slab allocation Sven Krohlas
2004-12-15 12:53   ` Jens Axboe
2004-12-15 12:35 krishna
  -- strict thread matches above, loose matches on Subject: below --
2004-12-15  3:48 krishna
2004-12-15  4:17 ` Mike Waychison

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=41C062E4.3030906@asbest-online.de \
    --to=sven@asbest-online.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox