From: Andi Kleen <andi@firstfloor.org>
To: Nick Piggin <npiggin@suse.de>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
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, 03 Apr 2008 10:41:13 +0200 [thread overview]
Message-ID: <87r6dns53q.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080403082650.GA20132@wotan.suse.de> (Nick Piggin's message of "Thu, 3 Apr 2008 10:26:51 +0200")
Nick Piggin <npiggin@suse.de> writes:
>
> 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? :)
Some networking workloads hit slab pretty aggressive (two
allocations per packet)
Just be careful with standard loopback, it has a contended lock
elsewhere
-Andi
next prev parent reply other threads:[~2008-04-03 8:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 7:25 [rfc] SLQB: YASA 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
2008-04-03 8:33 ` KOSAKI Motohiro
2008-04-03 8:41 ` Andi Kleen [this message]
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-08 18:51 ` Luiz Fernando N. Capitulino
2008-04-09 2:10 ` Nick Piggin
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=87r6dns53q.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=clameter@sgi.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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 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.