From patchwork Wed Nov 30 18:13:21 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Paul E. McKenney" X-Patchwork-Id: 13060203 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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 10D2AC4321E for ; Wed, 30 Nov 2022 18:13:31 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 7D19D6B0072; Wed, 30 Nov 2022 13:13:31 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 75A926B0073; Wed, 30 Nov 2022 13:13:31 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 5FC256B0074; Wed, 30 Nov 2022 13:13:31 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 50CB86B0072 for ; Wed, 30 Nov 2022 13:13:31 -0500 (EST) Received: from smtpin27.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 22330C0511 for ; Wed, 30 Nov 2022 18:13:31 +0000 (UTC) X-FDA: 80190906222.27.79A5D46 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf02.hostedemail.com (Postfix) with ESMTP id A563680019 for ; Wed, 30 Nov 2022 18:13:30 +0000 (UTC) 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 dfw.source.kernel.org (Postfix) with ESMTPS id 9D14461D54; Wed, 30 Nov 2022 18:13:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 16823C43155; Wed, 30 Nov 2022 18:13:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1669832008; bh=uYoVp3wfqf3fICtozjC2ekQQHH5L+XdF7tRF4atTO+Q=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=hkJumWSp1ikZCpXNqPUSCDnpFhz551D4U9Kk4eMWYUwEh5UqIy30sMH2g8L1UtMiy 7FphIoNYbtfdlUNTFX/BCIMtzBPo4pMetUOH2bKJ9hmmYGktR/W7is9KKoKtr/HkH2 mzVf0qcewBBpPecHuJ9AhrGl6qsru3qJlSA3NL4ZOp/izhZi3AgXH5K1Wx+oKjPNLR 92+bWi0y2zwX2rkYwjjEf0tEKKK2QtPxNd7VwnNiFKi+bvrH2EjtnXgHuuXfoHnSHw gjC8esHljhMc+IAiMsNlhd5C9exE4K3RwPYYsJA1Yp4O7P8OLU+tVMNi7zluyW8m5f tuenjVMK8X+Kw== Received: by paulmck-ThinkPad-P17-Gen-1.home (Postfix, from userid 1000) id 6BEBA5C1727; Wed, 30 Nov 2022 10:13:27 -0800 (PST) From: "Paul E. McKenney" To: rcu@vger.kernel.org Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com, rostedt@goodmis.org, "Joel Fernandes (Google)" , "Paul E . McKenney" , Dennis Zhou , Tejun Heo , Christoph Lameter , linux-mm@kvack.org Subject: [PATCH rcu 12/16] percpu-refcount: Use call_rcu_hurry() for atomic switch Date: Wed, 30 Nov 2022 10:13:21 -0800 Message-Id: <20221130181325.1012760-12-paulmck@kernel.org> X-Mailer: git-send-email 2.31.1.189.g2e36527f23 In-Reply-To: <20221130181316.GA1012431@paulmck-ThinkPad-P17-Gen-1> References: <20221130181316.GA1012431@paulmck-ThinkPad-P17-Gen-1> MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1669832010; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=opcgk9bN3S6Ta99hn9GnQg/Lq50u2zXrg/hR2h12HyA=; b=VoaTyx5TuVZjOf3h3weewQTWY9BRQe2b2lyMBMQf78RktZkX3MhfZQ+5mTSeshJKf4vvCe 3owDIC/Pz0WWC8bHgG4ahok85380ZZ4Lg8H6FKb8rKYme5n6TvgXC6iAc3vlssEGi7DdnL HwfKjl3/GMVCiWN9Y+ZH8OYbI23povo= ARC-Authentication-Results: i=1; imf02.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=hkJumWSp; spf=pass (imf02.hostedemail.com: domain of "SRS0=/+J4=36=paulmck-ThinkPad-P17-Gen-1.home=paulmck@kernel.org" designates 139.178.84.217 as permitted sender) smtp.mailfrom="SRS0=/+J4=36=paulmck-ThinkPad-P17-Gen-1.home=paulmck@kernel.org"; dmarc=pass (policy=none) header.from=kernel.org ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1669832010; a=rsa-sha256; cv=none; b=giCWaUC1bsF1yZJ+5y/GAN01frD48LcBe05JFdh+u0oMSBDLlik1pTwDXxbgXBzC5byisb V98I/VotMR1LNuJ1KYfplgo/lWqc1mNaV9f7lAMIWp2U1azG/v0cJWs3kQzbvwHh2+yQGw hT9ojndfF3VHnIljMQj2eAfin4Xj59Q= X-Stat-Signature: iet9n4z3ko4mqrasdem7h4p96fex3goo X-Rspamd-Queue-Id: A563680019 Authentication-Results: imf02.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=hkJumWSp; spf=pass (imf02.hostedemail.com: domain of "SRS0=/+J4=36=paulmck-ThinkPad-P17-Gen-1.home=paulmck@kernel.org" designates 139.178.84.217 as permitted sender) smtp.mailfrom="SRS0=/+J4=36=paulmck-ThinkPad-P17-Gen-1.home=paulmck@kernel.org"; dmarc=pass (policy=none) header.from=kernel.org X-Rspamd-Server: rspam06 X-Rspam-User: X-HE-Tag: 1669832010-559533 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: From: "Joel Fernandes (Google)" Earlier commits in this series allow battery-powered systems to build their kernels with the default-disabled CONFIG_RCU_LAZY=y Kconfig option. This Kconfig option causes call_rcu() to delay its callbacks in order to batch callbacks. This means that a given RCU grace period covers more callbacks, thus reducing the number of grace periods, in turn reducing the amount of energy consumed, which increases battery lifetime which can be a very good thing. This is not a subtle effect: In some important use cases, the battery lifetime is increased by more than 10%. This CONFIG_RCU_LAZY=y option is available only for CPUs that offload callbacks, for example, CPUs mentioned in the rcu_nocbs kernel boot parameter passed to kernels built with CONFIG_RCU_NOCB_CPU=y. Delaying callbacks is normally not a problem because most callbacks do nothing but free memory. If the system is short on memory, a shrinker will kick all currently queued lazy callbacks out of their laziness, thus freeing their memory in short order. Similarly, the rcu_barrier() function, which blocks until all currently queued callbacks are invoked, will also kick lazy callbacks, thus enabling rcu_barrier() to complete in a timely manner. However, there are some cases where laziness is not a good option. For example, synchronize_rcu() invokes call_rcu(), and blocks until the newly queued callback is invoked. It would not be a good for synchronize_rcu() to block for ten seconds, even on an idle system. Therefore, synchronize_rcu() invokes call_rcu_hurry() instead of call_rcu(). The arrival of a non-lazy call_rcu_hurry() callback on a given CPU kicks any lazy callbacks that might be already queued on that CPU. After all, if there is going to be a grace period, all callbacks might as well get full benefit from it. Yes, this could be done the other way around by creating a call_rcu_lazy(), but earlier experience with this approach and feedback at the 2022 Linux Plumbers Conference shifted the approach to call_rcu() being lazy with call_rcu_hurry() for the few places where laziness is inappropriate. And another call_rcu() instance that cannot be lazy is the one on the percpu refcounter's "per-CPU to atomic switch" code path, which uses RCU when switching to atomic mode. The enqueued callback wakes up waiters waiting in the percpu_ref_switch_waitq. Allowing this callback to be lazy would result in unacceptable slowdowns for users of per-CPU refcounts, such as blk_pre_runtime_suspend(). Therefore, make __percpu_ref_switch_to_atomic() use call_rcu_hurry() in order to revert to the old behavior. [ paulmck: Apply s/call_rcu_flush/call_rcu_hurry/ feedback from Tejun Heo. ] Signed-off-by: Joel Fernandes (Google) Signed-off-by: Paul E. McKenney Cc: Dennis Zhou Cc: Tejun Heo Cc: Christoph Lameter Cc: Acked-by: Tejun Heo --- lib/percpu-refcount.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lib/percpu-refcount.c b/lib/percpu-refcount.c index e5c5315da2741..668f6aa6a75de 100644 --- a/lib/percpu-refcount.c +++ b/lib/percpu-refcount.c @@ -230,7 +230,8 @@ static void __percpu_ref_switch_to_atomic(struct percpu_ref *ref, percpu_ref_noop_confirm_switch; percpu_ref_get(ref); /* put after confirmation */ - call_rcu(&ref->data->rcu, percpu_ref_switch_to_atomic_rcu); + call_rcu_hurry(&ref->data->rcu, + percpu_ref_switch_to_atomic_rcu); } static void __percpu_ref_switch_to_percpu(struct percpu_ref *ref)