Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp1727323pxb; Fri, 6 Nov 2020 18:42:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJyft97/KP/DYwNhOw/cnRawVhB+D4v+yC6J9vn7C4giAWpjGCS6lsKujINzqot4Y3e6bkIK X-Received: by 2002:a17:906:2932:: with SMTP id v18mr4976450ejd.144.1604716951833; Fri, 06 Nov 2020 18:42:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604716951; cv=none; d=google.com; s=arc-20160816; b=HZ1diunksWyL8pW1xS/cO39PZSSy3GrKLPDuxlTYJSq4+bqiLmHhmAtt25wkg7wX2j Jv9LFCC5P040Zq7z7blZ0vsKp5mkuKYtzco4lT/5L/o5C0pV8FnRGoWC4AoPsP2Q5bi+ re2/iGZfPp5X1Nowc4a8xhJy/PYiqOCIQ2P2ohXOvTgcfLC2+TgO2dVpYqfucdKPi8eE lOAKQxOT7zuWDKsBvNKkGI4JTkz7FyPWCYlC3uauMOW81hSlYgeWLTTANvuLwNgDdnlo qQV5zjwewys4r7ztj3nKeBk8kBUS9WRb2JgYJvJjMohymcif6xRLd7UEbcEQA+cO4+js SK8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=NmfJkUr47/qbZmh8BBeBQMH9XeFGsi1bLqgw6ySI+fs=; b=oqnHdSsB474ggW4499hl5FNXALhd1euOuQz9XrfJM42pYXq6x6IwqpZiVYG/NjKAAB QakTqtIeB24vAqa8YX9/nHD1f0cwYFNAuChfBrKUR3/vnyRhoTO9mKLosIczm3FkK35+ qT3YoAeQ48hWf4b1GWbslIQ5vyPD8U0i94qPPCxjRj8tKDk1i4fXxVG18dSsLxCWytsb +6qg/exWwqGeeo02Pflc+wGPD/9/EN369V4Pj1NfNtABTa5rGfS3ZoZHCjprnnN6rAPf 8yS2d6IFHWNHCj61yDif+VYUbV7OIUGgHl0BNL+gtNwOh8apAhiBZrNHY6v/s2YKu7KX Fr6g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u20si2287679ejt.331.2020.11.06.18.41.52; Fri, 06 Nov 2020 18:42:31 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728463AbgKGCcf (ORCPT + 99 others); Fri, 6 Nov 2020 21:32:35 -0500 Received: from netrider.rowland.org ([192.131.102.5]:52135 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1728110AbgKGCcf (ORCPT ); Fri, 6 Nov 2020 21:32:35 -0500 Received: (qmail 65132 invoked by uid 1000); 6 Nov 2020 21:32:14 -0500 Date: Fri, 6 Nov 2020 21:32:14 -0500 From: Alan Stern To: "Paul E. McKenney" Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, kernel-team@fb.com, mingo@kernel.org, parri.andrea@gmail.com, will@kernel.org, peterz@infradead.org, boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr, akiyks@gmail.com Subject: Re: [PATCH memory-model 5/8] tools/memory-model: Add a glossary of LKMM terms Message-ID: <20201107023214.GA64998@rowland.harvard.edu> References: <20201105215953.GA15309@paulmck-ThinkPad-P72> <20201105220017.15410-5-paulmck@kernel.org> <20201106165930.GC47039@rowland.harvard.edu> <20201106180445.GX3249@paulmck-ThinkPad-P72> <20201106192351.GA53131@rowland.harvard.edu> <20201106195912.GA3249@paulmck-ThinkPad-P72> <20201106204008.GA55521@rowland.harvard.edu> <20201106210413.GB3249@paulmck-ThinkPad-P72> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201106210413.GB3249@paulmck-ThinkPad-P72> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 06, 2020 at 01:04:13PM -0800, Paul E. McKenney wrote: > On Fri, Nov 06, 2020 at 03:40:08PM -0500, Alan Stern wrote: > > Is it really true that data dependencies are so easily destroyed? I > > would expect that a true "semantic" dependency (i.e., one where the > > value written really does vary according to the value read) would be > > rather hard to second guess. > > The usual optimizations apply, for but one example: > > r1 = READ_ONCE(x); > WRITE_ONCE(y, (r1 + 1) % MAX_ELEMENTS); > > If MAX_ELEMENTS is 1, so long, data dependency! Sure, but if MAX_ELEMENTS is 1 then the value written will always be 0 no matter what value r1 has, so it isn't a semantic dependency. Presumably a semantic data dependency would be much more robust. I wonder if it's worth pointing out this distinction to the reader. > With pointers, the compiler has fewer optimization opportunities, > but there are still cases where it can break the dependency. > Or transform it to a control dependency. Transforming a data dependency into a control dependency wouldn't make any important difference; the hardware would still provide the desired ordering. Alan