archive mirror
 help / color / mirror / Atom feed
From: "Uladzislau Rezki (Sony)" <>
To: Michal Hocko <>, Kees Cook <>,
	Shuah Khan <>,
	Andrew Morton <>,
Cc: LKML <>,
	Matthew Wilcox <>,
	Oleksiy Avramchenko <>,
	Thomas Gleixner <>,
	"Uladzislau Rezki (Sony)" <>
Subject: [RFC PATCH 0/1] test driver to analyse vmalloc allocator
Date: Tue, 13 Nov 2018 16:16:28 +0100	[thread overview]
Message-ID: <> (raw)


As an outcome of discussion there was
an interest in stress/performance test suite. It was developed to analyse
a vmalloc allocator from performance, stability point of view and compare
the new approach with current one.

I have explained in the commit message in detail how to use this test driver,
so please have look at: vmalloc: add test driver to analyse vmalloc allocator

I think it is pretty easy and handy to use. I am not sure if i need to create
kind of or in tools/testing/selftests/ to configure the test
module over misc device or so to apply different configurations and trigger
the test.

This driver uses one internal function that is not accessible from the kernel
module, thus as a workaround i use kallsyms_lookup_name("__vmalloc_node_range")
to find the symbol.

Also, i need to mention one thing here this test suite allowed me to identify
some issues in current design. So please refer to the link i pointed above.

Uladzislau Rezki (Sony) (1):
  vmalloc: add test driver to analyse vmalloc allocator

 lib/Kconfig.debug  |  12 ++
 lib/Makefile       |   1 +
 lib/test_vmalloc.c | 543 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 556 insertions(+)
 create mode 100644 lib/test_vmalloc.c


             reply	other threads:[~2018-11-13 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 15:16 Uladzislau Rezki (Sony) [this message]
2018-11-13 15:16 ` [RFC PATCH 1/1] vmalloc: add test driver to analyse vmalloc allocator Uladzislau Rezki (Sony)
2018-11-13 22:10   ` Andrew Morton
2018-11-14 15:17     ` Michal Hocko
2018-11-14 23:00       ` Andrew Morton
2018-11-15  8:39         ` Michal Hocko
2018-11-15  8:46           ` Matthew Wilcox
2018-11-15 12:57             ` Michal Hocko
2018-11-15 13:47               ` Matthew Wilcox
2018-11-15 20:57                 ` Andrew Morton
2018-11-15 12:36     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).