From: David Rientjes <rientjes@google.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Mel Gorman <mel@csn.ul.ie>,
linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>, Tejun Heo <tj@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
akpm@linux-foundation.org, Ingo Molnar <mingo@elte.hu>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [RFC In-kernel benchmarks 0/3] Introduce in kernel benchmarks
Date: Thu, 15 Oct 2009 01:09:28 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0910150107130.8299@chino.kir.corp.google.com> (raw)
In-Reply-To: <20091013200233.260324963@gentwo.org>
On Tue, 13 Oct 2009, Christoph Lameter wrote:
> In kernel benchmarks are benchmarks that directly run in kernel space.
>
> The test modules are regular kernel modules that can be loaded with
>
> modprobe slab_test
>
> or so.
>
> The initialization function of the module will then run the test
> and fail so that the module is not loaded. The output of the test
> results will be written to the system log.
>
> This is a rough draft. I have used these in the past to benchmark
> page allocator, slab allocator and vmstat performance.
>
I like the addition of these benchmarks to the kernel source, I've been
adding Mathieu's slab benchmark to my tree for a while. It looks like
they all need some degree of cleanup, though: they have checkpatch
warnings, they frequently do not handle memory allocation failures, and it
would be nice to have a consistent loglevel for all the results.
prev parent reply other threads:[~2009-10-15 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 20:02 Christoph Lameter
2009-10-13 20:02 ` [RFC In-kernel benchmarks 1/3] Add slab performance tests Christoph Lameter
2009-10-13 20:02 ` [RFC In-kernel benchmarks 2/3] Vm statistics performance test Christoph Lameter
2009-10-13 20:02 ` [RFC In-kernel benchmarks 3/3] Page allocator test Christoph Lameter
2009-10-15 8:09 ` David Rientjes [this message]
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=alpine.DEB.1.00.0910150107130.8299@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=tj@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
all inboxes | Powered by JetHome®