linux-kernel - Re: [GIT PULL] Locking changes for v4.2

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]

Date:	Fri, 26 Jun 2015 21:57:17 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Waiman Long <waiman.long@...com>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] Locking changes for v4.2

On Fri, 2015-06-26 at 13:27 -0400, Waiman Long wrote:

> I am glad that the qspinlock patch helps. May I know what kind of 
> machine (cpu type, # of sockets, etc) that you are running the test on? 
> Usually the more sockets the machine has, the bigger the improvement you 
> will see.

This particular host had two Intel(R) Xeon(R) CPU E5-2696 v2 @ 2.50GHz

(12 cores per socket, total of 48 hyper threads)

Note that if pipebench uses 48 threads (instead of 16 as my previous
mail did), there is almost no degradation.

lpaa23:~# ./pipebench -n 16
threads:16 sleep:30 pinned:1
total operations: 20228142, ops/sec 674271
20228142

lpaa23:~# ./pipebench -n 48
threads:48 sleep:30 pinned:1
total operations: 19763616, ops/sec 658787
19763616


Thanks

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