From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934555AbaFSUj4 (ORCPT ); Thu, 19 Jun 2014 16:39:56 -0400 Received: from qmta12.emeryville.ca.mail.comcast.net ([76.96.27.227]:36571 "EHLO qmta12.emeryville.ca.mail.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932343AbaFSUjz (ORCPT ); Thu, 19 Jun 2014 16:39:55 -0400 Date: Thu, 19 Jun 2014 15:39:52 -0500 (CDT) From: Christoph Lameter To: "Paul E. McKenney" cc: Linus Torvalds , Rusty Russell , Andrew Morton , Tejun Heo , David Howells , linux-kernel@vger.kernel.org, Oleg Nesterov Subject: Re: [PATCH RFC] percpu: add data dependency barrier in percpu accessors and operations In-Reply-To: <20140617195634.GQ4669@linux.vnet.ibm.com> Message-ID: References: <20140617144151.GD4669@linux.vnet.ibm.com> <20140617152752.GC31819@htj.dyndns.org> <20140617160040.GE31819@htj.dyndns.org> <20140617160508.GF31819@htj.dyndns.org> <20140617185510.GM4669@linux.vnet.ibm.com> <20140617195634.GQ4669@linux.vnet.ibm.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 17 Jun 2014, Paul E. McKenney wrote: > During operation that does not involve cross-CPU accesses, agreed. Well that is the typical operation mode for per cpu data and that is what it was made designed for.