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  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]
Date:	Fri, 8 Jan 2010 16:20:43 -0800
From:	"Paul E. McKenney" <>
To:	Mathieu Desnoyers <>
Cc:	Steven Rostedt <>,
	Oleg Nesterov <>,
	Peter Zijlstra <>,, Ingo Molnar <>,,,,,,,
Subject: Re: [RFC PATCH] introduce sys_membarrier(): process-wide memory

On Fri, Jan 08, 2010 at 06:53:38PM -0500, Mathieu Desnoyers wrote:
> * Steven Rostedt ( wrote:
> > Well, if we just grab the task_rq(task)->lock here, then we should be
> > OK? We would guarantee that curr is either the task we want or not.
> Hrm, I just tested it, and there seems to be a significant performance
> penality involved with taking these locks for each CPU, even with just 8
> cores. So if we can do without the locks, that would be preferred.

How significant?  Factor of two?  Two orders of magnitude?

							Thanx, Paul
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists