Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp8406677rwb; Wed, 23 Nov 2022 21:53:46 -0800 (PST) X-Google-Smtp-Source: AA0mqf5ptF+Ol6qXHAefRlT58OdzBNzky33pNVbd0inw2I0innMjIjPDiLaq93PphnZW9BKHV3It X-Received: by 2002:a05:6402:5307:b0:461:e3e1:bc3b with SMTP id eo7-20020a056402530700b00461e3e1bc3bmr14092593edb.145.1669269225720; Wed, 23 Nov 2022 21:53:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669269225; cv=none; d=google.com; s=arc-20160816; b=HnRLTZTU1x4syRkejDH+rMzVGKDXO3/PSADaa4gTaRDXy9mmtTN0lUKqfixhOkyudr gA5mhfKY3Kdk07WmZeN8RSafRNyl/0D0M4DDXzR7S/OtGC2Vye/91upMI76fS7GvIIVD SRqNK86S1QC5eAQ7uwMNJBW+V0xcdGXLEgIlsavJ0eO5GmkH4Ejifzxg0fEYoRAh4IpP eWXeUXe8hon99LQK8Iq7tgB60cd3lKmgfvZ7CxutcC/qqc31QMqYmmOoTr9uH8rsPBqW Pb2MuYhNNPwnBqwYbaKVtxkobYO4noZrMg37KVwgNhp48HogxT0L/KXLaV+Tloixt/9Y 9egA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=D0k6wwRzKVN96jAq/i+VwdgtpIY8xAcrQpLYHc7EjHk=; b=Drsj/nJirsdsPMtSyEusC2wlmVYDVNdPoF1hr9xBuycPd49jwBY2FR0hJt8bxemwa6 VUuhr4lhVgWnuwGzZl5vPLQATOrZ86oEFnK/XDI/F2+aWLoNUdcGwWRcP2Se5tfpzqP4 vOFJ0HHD57WEU01XMWVDh9UTSJ3RY0m18UXCYVQf6jLvOUWgh3rcHD0Fk4zMJPeB6jfM lqMShERPOCkGOO/VQdL4+Y/fhafmOrQJO/UcE2BejFKzEJfyHPXqIUqPx4uerABOzXqB trOmZljs20ageO8gDuyhdR1SbFTPuRtOmwV/Ljjh25EW+C0BG6Sg245gZuyIAYZpEDy7 Iclw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=ETnZPW79; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g10-20020a1709067c4a00b007ba28cd9ec5si106553ejp.217.2022.11.23.21.53.24; Wed, 23 Nov 2022 21:53:45 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=ETnZPW79; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S229490AbiKXF0G (ORCPT + 89 others); Thu, 24 Nov 2022 00:26:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45086 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229445AbiKXF0E (ORCPT ); Thu, 24 Nov 2022 00:26:04 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 642C3BF83F; Wed, 23 Nov 2022 21:26: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 19741B826A8; Thu, 24 Nov 2022 05:26:01 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C6B83C433C1; Thu, 24 Nov 2022 05:25:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1669267559; bh=nwU3BhTl4ZFKnyjDzaHonQhAXEgsrPOaMoGsP86wQuE=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=ETnZPW79F2nXruLCJHBtMGa2UOITLdj8D7mKYZUoY4ZoxORi/EpIdlFccvrKAglAF WXZhSyHOEJw8IrXCaNnoht1nd+ZriYZmVstX61ezfffyrsiJTAcVTJOY4adM4KvCzs vO3HutMVzoEQqjH03rFuHMnMbAvwvUlOEHxgKFR0h0gci28wRukbBG2rrw9enGvc/D XMLoeVzQUki6eB6j0n85xG+mkengoq36fZbfrGzqNVPTlar0j3XFeYu7FoufCKznsn u43LoiTXSnUct6BZ1pRJ0u/TU7AITBNgW3vnGus4FnUYuokliLz1IgBCtdWNeFkQIK u1a5WGuZ0JbIA== Received: by paulmck-ThinkPad-P17-Gen-1.home (Postfix, from userid 1000) id 6544F5C0DF2; Wed, 23 Nov 2022 21:25:59 -0800 (PST) Date: Wed, 23 Nov 2022 21:25:59 -0800 From: "Paul E. McKenney" To: "Zhang, Qiang1" Cc: Frederic Weisbecker , "joel@joelfernandes.org" , "rcu@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] srcu: Add detection of boot CPU srcu_data structure's->srcu_cblist Message-ID: <20221124052559.GP4001@paulmck-ThinkPad-P17-Gen-1> Reply-To: paulmck@kernel.org References: <20221117112050.3942407-1-qiang1.zhang@intel.com> <20221117142025.GE839309@lothringen> <20221123190456.GE4001@paulmck-ThinkPad-P17-Gen-1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 24, 2022 at 01:43:42AM +0000, Zhang, Qiang1 wrote: > On Wed, Nov 23, 2022 at 02:01:50AM +0000, Zhang, Qiang1 wrote: > > > > >On Thu, Nov 17, 2022 at 07:20:50PM +0800, Zqiang wrote: > > > Before SRCU_SIZE_WAIT_CALL srcu_size_state is reached, the srcu > > > callback only insert to boot-CPU srcu_data structure's->srcu_cblist > > > and other CPU srcu_data structure's->srcu_cblist is always empty. so > > > before SRCU_SIZE_WAIT_CALL is reached, need to correctly check boot-CPU > > > pend cbs in srcu_might_be_idle(). > > > > > > Signed-off-by: Zqiang > > > --- > > > kernel/rcu/srcutree.c | 7 +++++-- > > > 1 file changed, 5 insertions(+), 2 deletions(-) > > > > > > diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c > > > index 6af031200580..6d9af9901765 100644 > > > --- a/kernel/rcu/srcutree.c > > > +++ b/kernel/rcu/srcutree.c > > > @@ -1098,8 +1098,11 @@ static bool srcu_might_be_idle(struct srcu_struct *ssp) > > > unsigned long tlast; > > > > > > check_init_srcu_struct(ssp); > > > - /* If the local srcu_data structure has callbacks, not idle. */ > > > - sdp = raw_cpu_ptr(ssp->sda); > > > + /* If the boot CPU or local srcu_data structure has callbacks, not idle. */ > > > + if (smp_load_acquire(&ssp->srcu_size_state) < SRCU_SIZE_WAIT_CALL) > > > + sdp = per_cpu_ptr(ssp->sda, get_boot_cpu_id()); > > > + else > > > + sdp = raw_cpu_ptr(ssp->sda); > > > > > > > Hi Paul, > > > > For the convert_to_big default configuration(SRCU_SIZING_AUTO), I found that the srcu is in > > SRCU_SIZE_SMALL state most of the time in the system, I think this change is meaningful. > > > > Thoughts ? > > >You are right that this change might make srcu_might_be_idle() return a > >more accurate value in the common case. As things are now, some other > >CPU might just now have added a callback, but might not yet have started > >that new grace period. In that case, we might expedite an SRCU grace > >period when we would not have otherwise done so. However, this change > >would also increase contention on the get_boot_cpu_id() CPU's srcu_data > >structure's ->lock. > > > >So the result of that inaccurate return value is that the first two SRCU > >grace periods in a burst might be expedited instead of only the first one, > >and even then only if we hit a very narrow race window. > > > >Besides, this same thing can happen if two CPUs do synchronize_srcu() > >at the same time after a long-enough pause between grace periods. > >Both see no callbacks, so both ask for an expedited grace period. > >So again, the first two grace periods are expedited. > > > >As a result, I am having a very hard time justifying the increased > >lock contention. > > Thanks reply, I have another question, Is this srcu_data structure's->lock necessary? > the rcu_segcblist_pend_cbs() only check *tails[RCU_DONE_TAIL] is empty. > or can use rcu_segcblist_get_seglen(RCU_WAIT_TAIL + RCU_NEXT_READY_TAIL + RCU_NEXT_TAIL) > instead of rcu_segcblist_pend_cbs() to avoid locking? (although this is also inaccurate) That extra "*" means that the lock must be acquired. Otherwise, the pointed-to callback might even be unmapped between the time we fetched the pointer and the time we dereferenced it. Thanx, Paul. > Thanks > Zqiang > > > > >Am I missing something here? > > > > Thanx, Paul > > > > Thanks > > Zqiang > > > > > > >While at it if someone is interested in documenting/commenting on the meaning of > > >all these SRCU_SIZE_* things, it would be much appreciated! > > > > > >In the initial stage(SRCU_SIZE_SMALL), there is no srcu_node structures, only initialized > > >per-CPU srcu_data structures, at this time, we only use boot-cpu srcu_data structures's ->srcu_cblist > > >to store srcu callbacks. > > >if the contention of srcu_struct and srcu_data structure's->lock become busy, > > >transition to SRCU_SIZE_ALLOC. allocated memory for srcu_node structure at end of the SRCU > > >grace period. > > >if allocated success, transition to SRCU_SIZE_WAIT_BARRIER, in this state, invoke > > >srcu_barrier() will iterate over all possible CPUs, but we still only use boot-CPU srcu_cblist to store callbacks. > > >the task calling call_srcu() may have access to a new srcu_node structure or may not, > > >because call_srcu() is protected by SRCU, we may not transition to SRCU_SIZE_WAIT_CALL quickly, > > >need to wait in this state for a SRCU grace period to end. > > >After transition to SRCU_SIZE_WAIT_CALL, we enqueue srcu callbacks to own srcu_data structures's ->srcu_cblist. > > > > > >Does my description make my commit more detailed? > > > > > >Thanks > > >Zqiang > > > > > > > > > > > > > > > >Thanks. > > > > > > spin_lock_irqsave_rcu_node(sdp, flags); > > > if (rcu_segcblist_pend_cbs(&sdp->srcu_cblist)) { > > > spin_unlock_irqrestore_rcu_node(sdp, flags); > > > -- > > > 2.25.1 > > >