public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: npiggin@suse.de, manfred@colorfullife.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Simple Slab: A slab allocator with minimal meta information
Date: Wed, 9 Aug 2006 21:07:09 -0500	[thread overview]
Message-ID: <20060810020708.GN6908@waste.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0608091744290.4966@schroedinger.engr.sgi.com>

On Wed, Aug 09, 2006 at 05:52:00PM -0700, Christoph Lameter wrote:
> This is by no means complete and probably full of bugs. Feedback and help 
> wanted! I have tried to switch over two minor system caches (memory 
> policies) to use simple slab and it seems to work. We probably have some 
> way to go before we could do performance tests.

There's probably enough here to shim in a regular slab and kmalloc
interface layer to run a desktop machine.
 
> The Simple Slab is not NUMA capable at this point and I think the
> NUMAness may better be implemented in a different way. Maybe we
> could understand the Simple Slab as a lower layer and then add all
> the bells and whistles including NUMAness, proc API, kmalloc caches
> etc. on top as a management layer for this lower level
> functionality.

I think a layered approach to handling NUMA and the like makes an
awful lot of sense here. And probably greatly simplifies locking, etc.

Also, I like that you've gone to off-slab accounting. Not only does
this simplify things overall, it's good for memory footprint and
possibly better on cache footprint.

It's gonna need a better name though..

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2006-08-10  2:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  0:52 [RFC] Simple Slab: A slab allocator with minimal meta information Christoph Lameter
2006-08-10  2:07 ` Matt Mackall [this message]
2006-08-10  5:01 ` KAMEZAWA Hiroyuki
2006-08-10  5:13   ` Christoph Lameter
2006-08-10  5:44     ` KAMEZAWA Hiroyuki
2006-08-10  5:44       ` Christoph Lameter
2006-08-10  5:56         ` KAMEZAWA Hiroyuki
2006-08-10  6:13       ` KAMEZAWA Hiroyuki
2006-08-10 15:25         ` Christoph Lameter
2006-08-10 18:47           ` Manfred Spraul
2006-08-10 18:52             ` Christoph Lameter
2006-08-11 17:21             ` Christoph Lameter
2006-08-11 20:33               ` Manfred Spraul
2006-08-11 21:02                 ` Christoph Lameter
  -- strict thread matches above, loose matches on Subject: below --
2006-08-14  1:10 linux
2006-08-14 11:47 ` Andi Kleen

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=20060810020708.GN6908@waste.org \
    --to=mpm@selenic.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=npiggin@suse.de \
    /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