linux-kernel - Re: [PATCH 0/3] perf-bench: introduce futex microbenchmarks

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131216100828.GA21304@gmail.com>
Date:	Mon, 16 Dec 2013 11:08:28 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Davidlohr Bueso <davidlohr@...com>
Cc:	linux-kernel@...r.kernel.org, acme@...stprotocols.net,
	mingo@...hat.com, dvhart@...ux.intel.com, peterz@...radead.org,
	tglx@...utronix.de, jason.low2@...com, Waiman.Long@...com,
	scott.norton@...com, aswin@...com
Subject: Re: [PATCH 0/3] perf-bench: introduce futex microbenchmarks


* Davidlohr Bueso <davidlohr@...com> wrote:

> This patchset adds three programs that stress and measure different 
> futex operations: (i) uaddr hashing, (ii) wakeups and (iii) 
> requeuing/waiting.
> 
> More details and usage examples in each individual patch, along with 
> parameter descriptions in the code.
> 
> While the previous effort (https://lkml.org/lkml/2012/5/17/207) to 
> add futex benchmarks to perf-bench failed, I strongly believe that 
> perf is an ideal place for these kinds of programs. This patchset is 
> different from Hitoshi's because it does not try to take over 
> Darren's futextest suite, and only deals with finer grained aspects 
> of the kernel's implementation, and thus mostly useful for kernel 
> hacking. Furthermore, by being part of the kernel tree, it can get 
> more attention and naturally evolve with time.

Looks pretty useful!

Could the two approaches be merged?

Thanks,

	Ingo
--
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/