From: David Rientjes <rientjes@google.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Christoph Lameter <cl@linux.com>,
Glauber Costa <glommer@parallels.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Suleiman Souhlal <suleiman@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: object allocation benchmark
Date: Wed, 9 May 2012 15:24:25 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1205091523040.5041@chino.kir.corp.google.com> (raw)
In-Reply-To: <CAOJsxLEFsT3Ef9ztPnooJF2uSwELpkf90u_1=CtbvGGbO2LOiw@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 839 bytes --]
On Wed, 9 May 2012, Pekka Enberg wrote:
> >> I have some in kernel benchmarking tools for page allocator and slab
> >> allocators. But they are not really clean patches.
> >>
> >
> > This is the latest version of your tools that I have based on 3.3. Load
> > the modules with insmod and it will produce an error to automatically
> > unloaded (by design) and check dmesg for the results.
>
> Anyone interested in pushing the benchmark to mainline?
>
It's a pretty atypical type of a benchmark that must be compiled and
loaded as a benchmark for the most accurate results, I'm not sure if we
want to carry it in the kernel or not. I got these from when Christoph
initially sent them for your tree. If there's a renewed interest, let me
know and I'll send you the ported changes (pagealloc_test.c, slab_test.c,
and vmstat_test.c).
next prev parent reply other threads:[~2012-05-09 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 14:33 Glauber Costa
2012-03-19 15:28 ` Christoph Lameter
2012-03-19 20:41 ` David Rientjes
2012-05-09 6:24 ` Pekka Enberg
2012-05-09 22:24 ` David Rientjes [this message]
2012-03-22 14:22 ` Glauber Costa
2012-03-22 16:15 ` Christoph Lameter
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.2.00.1205091523040.5041@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=cl@linux.com \
--cc=glommer@parallels.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=suleiman@google.com \
/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