Received: by 2002:a25:1104:0:0:0:0:0 with SMTP id 4csp328510ybr; Fri, 22 May 2020 07:38:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxNpD6/X+E0DqqvMxTgRjRHSDB8gJXClxD5jKYSbH827ReUUeP4tQcOuINmYNDmkGt/lZpT X-Received: by 2002:a17:906:7e43:: with SMTP id z3mr8216173ejr.221.1590158293430; Fri, 22 May 2020 07:38:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590158293; cv=none; d=google.com; s=arc-20160816; b=EG1p6N5+bRh5C/1rFEg+6HjPWwYBraxkHL/1jdwTf/GwioQX0CMmdlk5Y2LPQWkpo6 OwfSNvYJTMlU05Nq65HuRUwecQYXYreZa9cH4TjCYYxEjRj3dLLIzUP8BcnGumg37/sT crliOQJp7zj07Lw33UTtJ2icVgfdahhfU+GYdU3TW0+k1A8aeuI8cQk1jADTGr0A7t9v lfPtaJJzwRQY0ihluW1Om1QjPBikm7eLx1VorYuSzJTffRJjm969obK5tAVjxwcWnPng 4rxxHoQrjCADKQW654cK6rSb22cb3me15HGLESQpmobmkYedFTqzkCQ+tbpLj46VMC0X 2hCQ== 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:message-id:subject:cc :to:from:date; bh=FmlSnMBul7Vg6SDbqbn/gtpZUBEn0VTXw2QPJPqunwA=; b=ppyCd8deOosRgJaXGRu8ytcmRCtVFByA2M4dWRBZIGcHURFQNLrw/zEZOcTemelGiT 2rL8Az7/1i7BVRwBREm2FdxKI06GRigCB1y/ENKYCPlrtDBKQJWzDNDOvWN0gLrwClBk YiqIa00kl6bAr8d+KdMLIoxoQWPvTpz+3rI6/DGuFpVlqNLd6G9Us6L+SbxekVCZ8/UR l9ZWSJWkw4z75iGG0bncSzotQFecK/1DKQ4mM7uzuB/M50dEC1S4+7pL1tKmx+gKEbTB v+GVjfO6KEEcPLC9YEiqVWjQSSY9A7JYK0T9m5DnNxlFqM74yZCJeyQOjTHtATpqbDr9 ikkQ== 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 y89si4390620eda.167.2020.05.22.07.37.48; Fri, 22 May 2020 07:38:13 -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; 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 S1729997AbgEVOgL (ORCPT + 99 others); Fri, 22 May 2020 10:36:11 -0400 Received: from netrider.rowland.org ([192.131.102.5]:53065 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1729879AbgEVOgK (ORCPT ); Fri, 22 May 2020 10:36:10 -0400 Received: (qmail 1718 invoked by uid 1000); 22 May 2020 10:36:09 -0400 Date: Fri, 22 May 2020 10:36:09 -0400 From: Alan Stern To: "Paul E. McKenney" Cc: Peter Zijlstra , 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: <20200522143609.GC32434@rowland.harvard.edu> References: <20200522003850.GA32698@paulmck-ThinkPad-P72> <20200522094407.GK325280@hirez.programming.kicks-ass.net> <20200522105659.GH2869@paulmck-ThinkPad-P72> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200522105659.GH2869@paulmck-ThinkPad-P72> User-Agent: Mutt/1.10.1 (2018-07-13) 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 03:56:59AM -0700, Paul E. McKenney wrote: > 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 wasn't the context in the litmus test. The context was: smp_wmb(); smp_store_release(); spin_unlock(); smp_store_release(); That certainly looks like a lot more ordering than is really needed. Alan