Received: by 10.223.185.116 with SMTP id b49csp717947wrg; Tue, 20 Feb 2018 06:49:05 -0800 (PST) X-Google-Smtp-Source: AH8x227YbOWlvstjRBisZjz2RE5Zr4+X1CmCtyuHsMlmWIR50nF/0+vKG1libN6krGjZoZ69KXUP X-Received: by 10.98.64.146 with SMTP id f18mr7117270pfd.30.1519138145769; Tue, 20 Feb 2018 06:49:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519138145; cv=none; d=google.com; s=arc-20160816; b=tvUdYanUfny8JqGIoaRXcAM3mszCrlcg7peBJAyNXnt3MBW6GYx2X5bJvssDTvdZhT svuXJ0LzQA/iG6rhZq35mr8acqgqQ9xrfSIZJmlAt9OvC/8CsLu80W67pF2C5CipLVCo sLG83zGcYOcYQIECjTOK/KGH4Qh7HVIDYlx8RE+yIUFbmpEfG23HWFHP7h3h9eEnxAPD Fr6s7BsQaW/t3HD+YrpyEopjOK8kZC6ZB95XHpE0zk6Sv59RhjFp8gAYLD+vW7BTdu5I 8/fsdRhptQuWAzHlGHV+ip+UQ+5jpcRCrGmsc1u32kkz3wPQfA1rHQNn488HerhyU8OH v0Ww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:user-agent:in-reply-to :content-disposition:mime-version:references:reply-to:subject:cc:to :from:date:arc-authentication-results; bh=HUJOiopfVKHCy6GfXVxXqB/BFGNX7lHJ6pej0cgNiqE=; b=kkrSt3DX6+GZv6/z2vz1L7cq5OzCtOCqcM3oGxUB2UCpHDTtjsy1OoelGwz/3XaBRY gb6UIdA4wxg/vAO0FFYrNqnC+KMThN6oijcyreEKeTvAtgKtlrlflF69rJib30sEiuUl N1mZnF5KIkmiDO74c0IFtOrgq7THhRin3tedNcHbwIlNv+58asu00GDMxnFVen59GSkk E27HSurodbLd+z/xQMJkuRp8RYbE7CBDgwF2JkkKBkUubbJfUF+WKLMnujWBQM/2A9sj c0uL00ZGZIBoKFLgLbgqHomlbp4ro/6PhGGV7LekY91mgrL2ruo5SC1MwYLpyI9c9aET ERJA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m11si1229437pgc.671.2018.02.20.06.48.50; Tue, 20 Feb 2018 06:49:05 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752017AbeBTOr7 (ORCPT + 99 others); Tue, 20 Feb 2018 09:47:59 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:45648 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751000AbeBTOr5 (ORCPT ); Tue, 20 Feb 2018 09:47:57 -0500 Received: from pps.filterd (m0098419.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w1KEiKVJ120405 for ; Tue, 20 Feb 2018 09:47:57 -0500 Received: from e12.ny.us.ibm.com (e12.ny.us.ibm.com [129.33.205.202]) by mx0b-001b2d01.pphosted.com with ESMTP id 2g8mjtuj0n-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 20 Feb 2018 09:47:57 -0500 Received: from localhost by e12.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 20 Feb 2018 09:47:56 -0500 Received: from b01cxnp22033.gho.pok.ibm.com (9.57.198.23) by e12.ny.us.ibm.com (146.89.104.199) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Tue, 20 Feb 2018 09:47:50 -0500 Received: from b01ledav003.gho.pok.ibm.com (b01ledav003.gho.pok.ibm.com [9.57.199.108]) by b01cxnp22033.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w1KElma938207586; Tue, 20 Feb 2018 14:47:50 GMT Received: from b01ledav003.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id AA004B2046; Tue, 20 Feb 2018 10:50:08 -0500 (EST) Received: from paulmck-ThinkPad-W541 (unknown [9.80.232.163]) by b01ledav003.gho.pok.ibm.com (Postfix) with ESMTP id 6CE48B2052; Tue, 20 Feb 2018 10:50:08 -0500 (EST) Received: by paulmck-ThinkPad-W541 (Postfix, from userid 1000) id A843E16C37B2; Tue, 20 Feb 2018 06:48:13 -0800 (PST) Date: Tue, 20 Feb 2018 06:48:13 -0800 From: "Paul E. McKenney" To: Peter Zijlstra Cc: Alan Stern , Andrea Parri , Akira Yokosawa , Kernel development list , mingo@kernel.org, Will Deacon , boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com, Jade Alglave , Luc Maranget , Patrick Bellasi Subject: Re: [PATCH] tools/memory-model: remove rb-dep, smp_read_barrier_depends, and lockless_dereference Reply-To: paulmck@linux.vnet.ibm.com References: <20180217151413.GA3785@andrea> <20180219174413.GV25201@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180219174413.GV25201@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 x-cbid: 18022014-0048-0000-0000-0000023C492D X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00008563; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000254; SDB=6.00992512; UDB=6.00504239; IPR=6.00771858; MB=3.00019656; MTD=3.00000008; XFM=3.00000015; UTC=2018-02-20 14:47:54 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18022014-0049-0000-0000-00004432052E Message-Id: <20180220144813.GF3617@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-02-20_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1802200188 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 19, 2018 at 06:44:13PM +0100, Peter Zijlstra wrote: > On Mon, Feb 19, 2018 at 12:14:45PM -0500, Alan Stern wrote: > > Note that operations like atomic_add_unless() already include memory > > barriers. > > It is valid for atomic_add_unless() to not imply any barriers when the > addition doesn't happen. Agreed, given that atomic_add_unless() just returns 0 or 1, not the pointer being added. Of course, the __atomic_add_unless() function that it calls is another story, as it does return the old value. Sigh. And __atomic_add_unless() is called directly from some code. All of which looks to be counters rather than pointers, thankfully. So, do we want to rely on atomic_add_unless() always being invoked on counters rather than pointers, or does it need an smp_read_barrier_depends()? Thanx, Paul