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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89997C4332F for ; Tue, 20 Dec 2022 22:58:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229720AbiLTW6S (ORCPT ); Tue, 20 Dec 2022 17:58:18 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51578 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234140AbiLTW6M (ORCPT ); Tue, 20 Dec 2022 17:58:12 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 377CB1F2F1; Tue, 20 Dec 2022 14:58:02 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id EAE67B81A01; Tue, 20 Dec 2022 22:58:00 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 271BCC433EF; Tue, 20 Dec 2022 22:57:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1671577079; bh=8+lijh8xkYJmCW+tgcGnoiFR5gOK2W4q0pc0yUXBS2w=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=hdjsc4KMNZycrNr4Kh6u0XxZnE8UVFNrAgQlXeYr8IUtudF+K9G8k53HrZSorZdqN d3gWl1tbuO8jWghgJbxNR2XuRaMx1Ts7FMznRo/hZG8TKbKHAsjG6SNGjUcEwETUCU x1jiEC3ptSHNdHFryr3BXldur0+N1fbUmJTTatKPqbXwx9vha14pA3FPy4NHExQJoM Q+xO9UdirY2zcEp8SCn5kS4Ggzyawo5fn7S7B1zi528meJur9GibenGyikCu+GKvG7 IvJBf8g3tpHOW0bRKGFBzgrUjVmiI85tZ3wJevcEvxLRXETqfIaNbg21LU8BwcV1to 5Kyk4J44Y8Qnw== Date: Tue, 20 Dec 2022 23:57:56 +0100 From: Frederic Weisbecker To: Mathieu Desnoyers Cc: Joel Fernandes , linux-kernel@vger.kernel.org, Josh Triplett , Lai Jiangshan , "Paul E. McKenney" , rcu@vger.kernel.org, Steven Rostedt Subject: Re: [RFC 0/2] srcu: Remove pre-flip memory barrier Message-ID: <20221220225756.GB26563@lothringen> References: <6438d903-ab97-48c7-c338-9f0bc2686f94@efficios.com> <7A9876BA-C375-42A7-A5C9-FD940D2898D7@joelfernandes.org> <5bd5ee4a-710a-96bc-abe8-772b2e60f478@efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5bd5ee4a-710a-96bc-abe8-772b2e60f478@efficios.com> Precedence: bulk List-ID: X-Mailing-List: rcu@vger.kernel.org On Tue, Dec 20, 2022 at 02:01:30PM -0500, Mathieu Desnoyers wrote: > On 2022-12-20 13:29, Joel Fernandes wrote: > > > > > I do want to finish my memory barrier studies of SRCU over the holidays since I have been deep in the hole with that already. Back to the post flip memory barrier here since I think now even that might not be needed… > > I strongly suspect the memory barrier after flip is useless for the same > reasons I mentioned explaining why the barrier before the flip is useless. > > However, we need to double-check that we have memory barriers at the > beginning and end of synchronize_srcu, and between load of "unlock" counters > and load of "lock" counters. > > Where is the barrier at the beginning of synchronize_srcu ? rcu_seq_snap() ? > > Thanks, > > Mathieu > > -- > Mathieu Desnoyers > EfficiOS Inc. > https://www.efficios.com >