linux-kernel - Re: [PATCH RFC] percpu: add data dependency barrier in percpu accessors and operations

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Jun 2014 17:15:43 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Christoph Lameter <cl@...two.org>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	David Howells <dhowells@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] percpu: add data dependency barrier in percpu
 accessors and operations

On Thu, Jun 19, 2014 at 04:11:47PM -0500, Christoph Lameter wrote:
> The aim of having percpu data is to have the ability for a processor to
> access memory dedicated to that processor in the fastest way possible by
> avoiding synchronization. You are beginning to add synchronization
> elements into the accesses of a processor to memory dedicated to its sole
> use.

Again, data dependency barrier is noop in all in-use archs.

> Remote write events are contrary to that design and are exceedingly rare.
> An IPI is justifiable for such a rare event. At least in my use cases I
> have always found that to be sufficient. Well, I designed the data
> structures in a way that made this possible because of the design criteria
> that did not allow me remote write access to other processors per cpu
> data.

You're repeatedly getting wayside in the discussion.  What are you
suggesting?  Sending IPIs on each percpu allocation?

Again, I'm leaning towards just clarifying the init write ownership to
the allocating CPU as that seems the most straight forward way to deal
with it, but please stop brining up the raw performance thing.  Nobody
is doing anything to that.  It's not relevant in the discussion.

Thanks.

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