From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751979Ab1LLIzl (ORCPT ); Mon, 12 Dec 2011 03:55:41 -0500 Received: from casper.infradead.org ([85.118.1.10]:43112 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751125Ab1LLIzg convert rfc822-to-8bit (ORCPT ); Mon, 12 Dec 2011 03:55:36 -0500 Message-ID: <1323680078.16764.45.camel@twins> Subject: Re: [PATCH 3/3] kref: Remove the memory barriers From: Peter Zijlstra To: Ming Lei Cc: gregkh@suse.de, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, ostrikov@nvidia.com, adobriyan@gmail.com, eric.dumazet@gmail.com, mingo@elte.hu, Oliver Neukum Date: Mon, 12 Dec 2011 09:54:38 +0100 In-Reply-To: References: <20111210104341.592561407@chello.nl> <20111210104840.295857663@chello.nl> <1323529084.16764.5.camel@twins> <1323546551.2822.14.camel@laptop> <1323607627.16764.13.camel@twins> <1323617738.16764.21.camel@twins> <1323636148.16764.44.camel@twins> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Mailer: Evolution 3.2.1- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2011-12-12 at 11:48 +0800, Ming Lei wrote: > For kref, maybe it is still multiple operations done on one cpu vs them > being visible on another, but seems a bit implicit, see the common kref > usage below: > > CPU0 CPU1 > A:kref_init(&obj->ref) how does CPU0 get a ref to obj? > B:kref_get(&obj->ref) > C:access obj E:access obj > F:kref_put(&ojb->ref) > D:kref_put(obj->ref)