linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, Kees Cook <keescook@chromium.org>,
	Matthew Wilcox <willy@infradead.org>,
	linux-mm@kvack.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>,
	Thomas Gleixner <tglx@linutronix.de>, shuah <shuah@kernel.org>
Subject: Re: [RFC PATCH 3/3] selftests/vm: add script helper for CONFIG_TEST_VMALLOC_MODULE
Date: Fri, 4 Jan 2019 11:34:30 -0700	[thread overview]
Message-ID: <d62089c4-8225-6363-1de5-ff2e8a3f684e@kernel.org> (raw)
In-Reply-To: <20190103142108.20744-4-urezki@gmail.com>

On 1/3/19 7:21 AM, Uladzislau Rezki (Sony) wrote:
> Add the test script for the kernel test driver to analyse vmalloc
> allocator for benchmarking and stressing purposes. It is just a kernel
> module loader. You can specify and pass different parameters in order
> to investigate allocations behaviour. See "usage" output for more
> details.
> 
> Also add basic vmalloc smoke test to the "run_vmtests" suite.
> 
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> ---

Thanks for adding skip handling. Here is my

Reviewed-by: Shuah Khan <shuah@kernel.org>

for Andrew to take this through mm tree.

thanks,
-- Shuah

  reply	other threads:[~2019-01-04 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 14:21 [RFC PATCH v4 0/3] test driver to analyse vmalloc allocator Uladzislau Rezki (Sony)
2019-01-03 14:21 ` [RFC PATCH 1/3] vmalloc: export __vmalloc_node_range for CONFIG_TEST_VMALLOC_MODULE Uladzislau Rezki (Sony)
2019-01-03 14:21 ` [RFC PATCH 2/3] vmalloc: add test driver to analyse vmalloc allocator Uladzislau Rezki (Sony)
2019-01-03 14:21 ` [RFC PATCH 3/3] selftests/vm: add script helper for CONFIG_TEST_VMALLOC_MODULE Uladzislau Rezki (Sony)
2019-01-04 18:34   ` shuah [this message]
2019-01-05 17:53     ` Uladzislau Rezki

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=d62089c4-8225-6363-1de5-ff2e8a3f684e@kernel.org \
    --to=shuah@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=oleksiy.avramchenko@sonymobile.com \
    --cc=tglx@linutronix.de \
    --cc=urezki@gmail.com \
    --cc=willy@infradead.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