From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Jesper Dangaard Brouer <brouer@redhat.com>
Cc: linux-mm <linux-mm@kvack.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Subject: Re: Memory exhaustion testing?
Date: Fri, 20 Nov 2015 15:23:09 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1511201522150.10092@chino.kir.corp.google.com> (raw)
In-Reply-To: <20151120140916.33ec7896@redhat.com>
On Fri, 20 Nov 2015, Jesper Dangaard Brouer wrote:
> > Any chance you could proffer some of your scripts in the form of patches
> > to the tools/testing directory? Anything that can reliably trigger rarely
> > executed code is always useful.
>
> Perhaps that is a good idea.
>
> I think should move the directory location in my git-repo
> prototype-kernel[1] to reflect this directory layout, like I do with
> real kernel stuff. And when we are happy with the quality of the
> scripts we can "move" it to the kernel. (Like I did with my pktgen
> tests[4], now located in samples/pktgen/).
>
> A question; where should/could we place the kernel module
> slab_bulk_test04_exhaust_mem[1] that my fail01 script depends on?
>
I've had the same question because I'd like to add slab and page allocator
benchmark modules originally developed by Christoph Lameter to the tree.
Let's add Andrew.
--
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:[~2015-11-20 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 20:55 Jesper Dangaard Brouer
2015-11-13 22:54 ` David Rientjes
2015-11-16 14:24 ` Jesper Dangaard Brouer
2015-11-17 13:21 ` Jesper Dangaard Brouer
2015-11-19 20:40 ` David Rientjes
2015-11-20 13:09 ` Jesper Dangaard Brouer
2015-11-20 23:23 ` David Rientjes [this message]
2015-11-20 23:28 ` Andrew Morton
2015-11-14 8:23 ` Tetsuo Handa
2015-11-16 14:43 ` Jesper Dangaard Brouer
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.10.1511201522150.10092@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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