From: Christoph Lameter <cl@gentwo.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Wei Yang <weiyang@linux.vnet.ibm.com>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: mm: slub: invalid memory access in setup_object
Date: Wed, 2 Jul 2014 09:44:57 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.11.1407020935450.17773@gentwo.org> (raw)
In-Reply-To: <53B32D80.8000601@oracle.com>
On Tue, 1 Jul 2014, Sasha Levin wrote:
> Is there a better way to stress test slub?
The typical way to test is by stressing the network subsystem
with small packets that require small allocations. Or do a filesystem
test that requires lots of metadata (file creations, removal, renames
etc).
But I also posted some in kernel benchmarks a while back
https://lkml.org/lkml/2009/10/13/459
Pekka had a project going to get these merged.
https://lkml.org/lkml/2009/11/29/17
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-07-02 14:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 16:51 Sasha Levin
2014-06-25 17:30 ` Christoph Lameter
2014-06-30 22:03 ` David Rientjes
2014-07-01 1:40 ` Wei Yang
2014-07-01 14:58 ` Christoph Lameter
2014-07-01 21:49 ` Andrew Morton
2014-07-01 21:52 ` Sasha Levin
2014-07-02 14:44 ` Christoph Lameter [this message]
2014-07-02 2:06 ` Wei Yang
2014-07-02 15:07 ` Christoph Lameter
2014-07-03 2:23 ` Wei Yang
2014-07-02 2:04 ` Wei Yang
2014-07-02 14:20 ` Christoph Lameter
2014-07-03 12:40 ` Wei Yang
2014-07-07 13:51 ` Christoph Lameter
2014-07-08 1:34 ` Wei Yang
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.11.1407020935450.17773@gentwo.org \
--to=cl@gentwo.org \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.com \
--cc=weiyang@linux.vnet.ibm.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