Received: by 2002:a25:1104:0:0:0:0:0 with SMTP id 4csp172801ybr; Fri, 22 May 2020 03:59:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxcM7K/TDMzzn81JaYdwrbHgO6rlQi0dH8UBRS/BMbxmBoQCXXPXnmVv06uJjQjb6TRva6Y X-Received: by 2002:a17:906:4886:: with SMTP id v6mr7792073ejq.11.1590145142104; Fri, 22 May 2020 03:59:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590145142; cv=none; d=google.com; s=arc-20160816; b=kDfrtOqFBRBR6Pfihz05vhllaT3sunsE9/czyZKaD1uWNaFuLTCXLVICfL5artjVAs ijc1omgyLHRQz6Vth9Fabvh4WXVrUCaWNI35mHlB3w6qo0Y2KGhbmkUDTJCqErB8RuvO HMP4sqiTGh6a+tr4g2ws9L7eiBvJ7RRhHHPNoaMafcUICOAJW5g+ITr8MarbmAQPtFF1 QYD4iQi9cNjcm5Z6ibFyxweCy5eoRpOGFUy5HRnakPEp7achW6yvjkDsLbP+BhLLk3Gw rV9EWpclkMZM11lRQ7X8RTIt3VsAgZGRCTtybIe3/6EhnHW1Rv/ctay+kAULpkZFScTr 14+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:reply-to:message-id :subject:cc:to:from:date:dkim-signature; bh=R54Iry4jHxirRXLrG+b3GFVMy+tZivYxQzDTTa/iAhY=; b=c20tPb3MZt504YSaeVIGDa9psOD8tfbRlRWSaSsgcDl860G11mqUHbyi5Y9APw4yVi K5rclJMcNUE/VBNzGOvz4XJUIksBVkdOOLGNTskh63v5ospuvn1yqDwZSjKgw+YtK/WM 0Zo1EBndhc7H0rIAeC1+W00NlqUDd6l2QMdVWFyX3mN6I0eyBrMVi+BIsq9AFZ8w3wkB 6WSOrU6vcdaMK5CYG6VaUBuvAQ1R96Lqak/M0OAUDSZ5Cl506YRE18fh7MiUOnE2bpvq oYyk0yySBJW7n0iHDOjylciDfpuww7F4RAKwZT9xB8tpFQU4CsvASzz6YGmma+vqhIba snsw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=S5BAtuOq; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k13si4570055edn.344.2020.05.22.03.58.37; Fri, 22 May 2020 03:59:02 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=default header.b=S5BAtuOq; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728871AbgEVK5A (ORCPT + 99 others); Fri, 22 May 2020 06:57:00 -0400 Received: from mail.kernel.org ([198.145.29.99]:56712 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728371AbgEVK5A (ORCPT ); Fri, 22 May 2020 06:57:00 -0400 Received: from paulmck-ThinkPad-P72.home (50-39-105-78.bvtn.or.frontiernet.net [50.39.105.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C6A0020679; Fri, 22 May 2020 10:56:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1590145019; bh=Lh7d7fjKNY7SzfKndVpbX94Aqe2UUFTEu4zvw1niz+o=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=S5BAtuOqFeMMeXX6M2mkB76V1Iyu66qYTRsNdlNuNl4VhAbwmtMe7+wmYggLrdEQ8 lg+uMd/4lEJwbuCjRJT/hQU9v2sFiAgQnL9jBi0Uviqv0SuH69OewBruLrEhajMcmL Phhh0XdHAXukgp1qpLC9s40OnMa8UpuINo4Kstc0= Received: by paulmck-ThinkPad-P72.home (Postfix, from userid 1000) id 8170A3520C6D; Fri, 22 May 2020 03:56:59 -0700 (PDT) Date: Fri, 22 May 2020 03:56:59 -0700 From: "Paul E. McKenney" To: Peter Zijlstra Cc: stern@rowland.harvard.edu, parri.andrea@gmail.com, will@kernel.org, boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr, akiyks@gmail.com, dlustig@nvidia.com, joel@joelfernandes.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, andriin@fb.com Subject: Re: Some -serious- BPF-related litmus tests Message-ID: <20200522105659.GH2869@paulmck-ThinkPad-P72> Reply-To: paulmck@kernel.org References: <20200522003850.GA32698@paulmck-ThinkPad-P72> <20200522094407.GK325280@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200522094407.GK325280@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 22, 2020 at 11:44:07AM +0200, Peter Zijlstra wrote: > On Thu, May 21, 2020 at 05:38:50PM -0700, Paul E. McKenney wrote: > > Hello! > > > > Just wanted to call your attention to some pretty cool and pretty serious > > litmus tests that Andrii did as part of his BPF ring-buffer work: > > > > https://lore.kernel.org/bpf/20200517195727.279322-3-andriin@fb.com/ > > > > Thoughts? > > I find: > > smp_wmb() > smp_store_release() > > a _very_ weird construct. What is that supposed to even do? Indeed, and I asked about that in my review of the patch containing the code. It -could- make sense if there is a prior read and a later store: r1 = READ_ONCE(a); WRITE_ONCE(b, 1); smp_wmb(); smp_store_release(&c, 1); WRITE_ONCE(d, 1); So a->c and b->c is smp_store_release() and b->d is smp_wmb(). But if there were only stores, the smp_wmb() would suffice. And if there wasn't the trailing store, smp_store_release() would suffice. But that would at least want a comment, in my opinion. ;-) Thanx, Paul