From: Nick Piggin <npiggin@suse.de>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [rfc] SLQB: YASA
Date: Thu, 3 Apr 2008 10:26:51 +0200 [thread overview]
Message-ID: <20080403082650.GA20132@wotan.suse.de> (raw)
In-Reply-To: <20080403171626.0283.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Thu, Apr 03, 2008 at 05:17:39PM +0900, KOSAKI Motohiro wrote:
> Hi
>
> > > Why is this not a patch set against SLUB?
> >
> > It's a completely different design of the core allocator algorithms
> > really.
> >
> > It probably looks quite similar because I started with slub.c, but
> > really is just the peripheral supporting code and structure. I'm never
> > intending to try to go through the pain of incrementally changing SLUB
> > into SLQB. If SLQB is found to be a good idea, then it could maybe get
> > merged.
>
> Do you have performance mesurement result?
> I hope see it if possible.
>
> Thanks! :)
Nothing really interesting, unfortunately. I have run some tests on
various microbenchmarks like tbench and things like that. But I
don't have many good ideas for more meaningful tests where slab
allocation performance is critial. Any suggestions? :)
Thanks,
Nick
next prev parent reply other threads:[~2008-04-03 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 7:25 Nick Piggin
2008-04-03 7:45 ` Pekka Enberg
2008-04-03 7:57 ` Nick Piggin
2008-04-03 8:13 ` Nick Piggin
2008-04-03 8:24 ` Pekka Enberg
2008-04-03 8:32 ` Nick Piggin
2008-04-03 8:17 ` KOSAKI Motohiro
2008-04-03 8:26 ` Nick Piggin [this message]
2008-04-03 8:33 ` KOSAKI Motohiro
2008-04-03 8:41 ` Andi Kleen
2008-04-03 14:23 ` Nick Piggin
2008-04-03 19:04 ` Luiz Fernando N. Capitulino
2008-04-03 19:12 ` Christoph Lameter
2008-04-08 11:57 ` Nick Piggin
2008-04-08 18:51 ` Luiz Fernando N. Capitulino
2008-04-09 2:10 ` Nick Piggin
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=20080403082650.GA20132@wotan.suse.de \
--to=npiggin@suse.de \
--cc=clameter@sgi.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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