From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 92799C43142 for ; Thu, 28 Jun 2018 13:52:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8BD8627429 for ; Thu, 28 Jun 2018 13:52:18 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=amarulasolutions.com header.i=@amarulasolutions.com header.b="nUQMLk04" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8BD8627429 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=amarulasolutions.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966325AbeF1NwQ (ORCPT ); Thu, 28 Jun 2018 09:52:16 -0400 Received: from mail-wm0-f43.google.com ([74.125.82.43]:39579 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965989AbeF1NwP (ORCPT ); Thu, 28 Jun 2018 09:52:15 -0400 Received: by mail-wm0-f43.google.com with SMTP id p11-v6so9111658wmc.4 for ; Thu, 28 Jun 2018 06:52:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=9IsqMTmPfoOWC8YQ7OF+QZpnRr3INUW4vs303iXWhuk=; b=nUQMLk04i6l1kDurgFefITkbCqPFDDmXrWym2B8HVKjkc11CpCbTlW+YpyY909I50R fSsT2eGm3QlCBw6MWT3MGHg//88/8OzudickrgP3rUzVUCsT9UDWrE3MIQmOb5XqPiCy u/obY/1UT0ZAeCG16FsaSzgUFKqbyF3RIMGXM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=9IsqMTmPfoOWC8YQ7OF+QZpnRr3INUW4vs303iXWhuk=; b=eCijVnl9Qy/Wsz8UNQl7Ebdprgvjski6/NDlw0Sf5ytOlvbUF0ei+suiKo5MdV+knl S6e1fr/T8YfGq4W9ocyAoOuj3wpKzZjaauekeBQOPhyMm95Qzq0DTLENusJmomx01lgj RMEArI/8kP5vQDnrdbGar8zfyz83HwrH0aTExWm5jzkXBGHa0UF5FX9Emaqz3gDnzL1c hKKdVAglNDJF15a7ju8lgdrXqqQzyvB8/7rlrgI0/KlmKizULtdMJA8P5HtZ6WTHReqs ImSKeWwQJMA9lLyo5YFizz2Xc5GDa1YLuQshYuNbsklIZezs+fMunl7uxPRUoBr/odH5 CwaA== X-Gm-Message-State: APt69E2Dy2OKBNGN4eCE23vKfX5QyApEq4D7Mzng+hirT1E/3E9Wx3Pr 1IDvDg4ufNVwYdlrG8UcsG38xA== X-Google-Smtp-Source: AAOMgpeOwOJ6TedpePJkX495j7sfDWjRncvQTU9k2UNayZCP/Tg2pyIIiKk/jAs5JwmgtUsXilJKfw== X-Received: by 2002:a1c:9788:: with SMTP id z130-v6mr8695704wmd.88.1530193933833; Thu, 28 Jun 2018 06:52:13 -0700 (PDT) Received: from andrea (85.100.broadband17.iol.cz. [109.80.100.85]) by smtp.gmail.com with ESMTPSA id s3-v6sm7964962wrp.76.2018.06.28.06.52.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Jun 2018 06:52:13 -0700 (PDT) Date: Thu, 28 Jun 2018 15:52:06 +0200 From: Andrea Parri To: Alan Stern Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, Peter Zijlstra , Ingo Molnar , Will Deacon , Boqun Feng , Nicholas Piggin , David Howells , Jade Alglave , Luc Maranget , "Paul E . McKenney" , Akira Yokosawa , Daniel Lustig , Jonathan Corbet , Randy Dunlap Subject: Re: [PATCH 2/3] locking: Clarify requirements for smp_mb__after_spinlock() Message-ID: <20180628135206.GA16107@andrea> References: <1530182480-13205-3-git-send-email-andrea.parri@amarulasolutions.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > + * smp_mb__after_spinlock() provides a full memory barrier between po-earlier > > + * lock acquisitions and po-later memory accesses. > > How about saying "provides the equivalent of a full memory barrier"? > > The point being that smp_mb__after_spinlock doesn't have to provide an > actual barrier; it just has to ensure the behavior is the same as if a > full barrier were present. Agreed; will fix in the next version. Thanks, Andrea > > Alan > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-5.6 required=5.0 tests=DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id B90CB7D043 for ; Thu, 28 Jun 2018 13:52:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966260AbeF1NwQ (ORCPT ); Thu, 28 Jun 2018 09:52:16 -0400 Received: from mail-wm0-f46.google.com ([74.125.82.46]:35110 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966009AbeF1NwP (ORCPT ); Thu, 28 Jun 2018 09:52:15 -0400 Received: by mail-wm0-f46.google.com with SMTP id z137-v6so9199064wmc.0 for ; Thu, 28 Jun 2018 06:52:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=9IsqMTmPfoOWC8YQ7OF+QZpnRr3INUW4vs303iXWhuk=; b=nUQMLk04i6l1kDurgFefITkbCqPFDDmXrWym2B8HVKjkc11CpCbTlW+YpyY909I50R fSsT2eGm3QlCBw6MWT3MGHg//88/8OzudickrgP3rUzVUCsT9UDWrE3MIQmOb5XqPiCy u/obY/1UT0ZAeCG16FsaSzgUFKqbyF3RIMGXM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=9IsqMTmPfoOWC8YQ7OF+QZpnRr3INUW4vs303iXWhuk=; b=VBTJ19sLYWrl9XG2OgZvjzkxnykuaaTa8Tv0aEVvSj4P0KVH4qozcG5lHUrI1I5P0f WZqx3OppH8TQW9xz+MEyvISOqb+qGvApEfw7Pphfj5B7VV06FIjtCFvUkbYejdaLrxcM KC09mE2qzvZMtFCdOrfxCHvLqi+tjdHrrKcwSIJxVZsZCpJZPRQWsx6zSzj+mNJCwFNp C133MLqvqzbn5TUMtKSKKSB8OTn/dH40wON44jCSUt5z9tO2fuZVEXFwKHAvdreEw15M /2I6ThhqIjglXGpWH94h4G/Kk+bOrB00tG0SNCFwRNrxJokG44KhkYMpBBVSKu1IZh5G LuJQ== X-Gm-Message-State: APt69E2OMa6RCKCvDtTGpVC4tz9GVe+0ij17YjuZqcY+psi/hKZLvFNK AangIRPSMxd0GYgzS7EN1sn48g== X-Google-Smtp-Source: AAOMgpeOwOJ6TedpePJkX495j7sfDWjRncvQTU9k2UNayZCP/Tg2pyIIiKk/jAs5JwmgtUsXilJKfw== X-Received: by 2002:a1c:9788:: with SMTP id z130-v6mr8695704wmd.88.1530193933833; Thu, 28 Jun 2018 06:52:13 -0700 (PDT) Received: from andrea (85.100.broadband17.iol.cz. [109.80.100.85]) by smtp.gmail.com with ESMTPSA id s3-v6sm7964962wrp.76.2018.06.28.06.52.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Jun 2018 06:52:13 -0700 (PDT) Date: Thu, 28 Jun 2018 15:52:06 +0200 From: Andrea Parri To: Alan Stern Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, Peter Zijlstra , Ingo Molnar , Will Deacon , Boqun Feng , Nicholas Piggin , David Howells , Jade Alglave , Luc Maranget , "Paul E . McKenney" , Akira Yokosawa , Daniel Lustig , Jonathan Corbet , Randy Dunlap Subject: Re: [PATCH 2/3] locking: Clarify requirements for smp_mb__after_spinlock() Message-ID: <20180628135206.GA16107@andrea> References: <1530182480-13205-3-git-send-email-andrea.parri@amarulasolutions.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org > > + * smp_mb__after_spinlock() provides a full memory barrier between po-earlier > > + * lock acquisitions and po-later memory accesses. > > How about saying "provides the equivalent of a full memory barrier"? > > The point being that smp_mb__after_spinlock doesn't have to provide an > actual barrier; it just has to ensure the behavior is the same as if a > full barrier were present. Agreed; will fix in the next version. Thanks, Andrea > > Alan > -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html