lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.00.0910150107130.8299@chino.kir.corp.google.com>
Date:	Thu, 15 Oct 2009 01:09:28 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Christoph Lameter <cl@...ux-foundation.org>
cc:	Mel Gorman <mel@....ul.ie>, linux-kernel@...r.kernel.org,
	Pekka Enberg <penberg@...helsinki.fi>,
	Tejun Heo <tj@...nel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	akpm@...ux-foundation.org, Ingo Molnar <mingo@...e.hu>,
	Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: [RFC In-kernel benchmarks 0/3] Introduce in kernel benchmarks

On Tue, 13 Oct 2009, Christoph Lameter wrote:

> In kernel benchmarks are benchmarks that directly run in kernel space.
> 
> The test modules are regular kernel modules that can be loaded with
> 
> 	modprobe slab_test
> 
> or so. 
> 
> The initialization function of the module will then run the test
> and fail so that the module is not loaded. The output of the test
> results will be written to the system log.
> 
> This is a rough draft. I have used these in the past to benchmark
> page allocator, slab allocator and vmstat performance.
> 

I like the addition of these benchmarks to the kernel source, I've been 
adding Mathieu's slab benchmark to my tree for a while.  It looks like 
they all need some degree of cleanup, though: they have checkpatch 
warnings, they frequently do not handle memory allocation failures, and it 
would be nice to have a consistent loglevel for all the results.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ