Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp4636205rdb; Tue, 12 Dec 2023 05:28:28 -0800 (PST) X-Google-Smtp-Source: AGHT+IFIVq/jI/nGBfBF1dXIR3PSZJqml10Uw8lkjk9llqGuyLtFZ/1ezQk34WSpo+AVd8XfO77I X-Received: by 2002:a92:c54d:0:b0:35d:78de:237e with SMTP id a13-20020a92c54d000000b0035d78de237emr9440387ilj.27.1702387708272; Tue, 12 Dec 2023 05:28:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702387708; cv=none; d=google.com; s=arc-20160816; b=FWDYaUT2jOrWU7vM8fMBwb1n1+aPLemgpK9gvK8GuYNje4WbFDqToQ/xJzE0IBHxOy FzYiN1gYkcogsrKLuD6cD7DUYxKc3KO829HzC4Fvrf7BtbaOHs19AbXdqVI1dEt0G+t2 P1WZ9IyhdNdGo469b495RDjwiSSPsh+qRQ1vuw08eQUSpE2lXXYtR2AWbwmcvU0rr6e/ wv07MOOEbR3Q9CBh5CDfq/ByiBGwGrFdyt/2s87yP5XeEJeE9y+UIiEnk7shwbSX4UWa KxKLBrKEHOhSEqZuk/blhUCXXECIuIGZbj3sCQqWid0tos7sLpcp76LZowuj4Xze77qy xcRQ== 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-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=ptMajJ7olP6/I9Dsx4zfbqiLHVy9K6V09svRxW7dXHQ=; fh=z/vsNFaVr3HzCqqa1yWn+zXskoty2SVgF1UwvVLIkZo=; b=r2MwqFR6zXnGGLNGCxOzhW26ChBDbnzGIwo9T3gbof5kda5s2avBJ/raRGaw9V1BR1 vQUxtzqId4ck0wvSNu5mWNJr/HYmBDZLeOXY2wI7OBY2t7mGtTyX+O5b8EfhmW2qdePx hSiPUOts6B0PkPuotekhH6Sukvr61jZ0exhQIxyJiONUP6NYNlIrj8c6kCDRvuXecm04 ZGsKN7mMTzwA4AHZf0hN+sRhQsY1CLwV0uxSadcru+cBiW/1lJNwUQCzCznAsJ/6ME2J 4JNXlQizyaTCIi1ec59KdWyKPb9ZkstIB5LY83X0ztJrwohy1fYxvGSgSBzQJnHMcE02 R+gg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=fZ79lRiY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 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 lipwig.vger.email (lipwig.vger.email. [23.128.96.33]) by mx.google.com with ESMTPS id u10-20020a63140a000000b005c684e1f2c8si7466956pgl.371.2023.12.12.05.28.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Dec 2023 05:28:28 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=fZ79lRiY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id D0E30804C4A4; Tue, 12 Dec 2023 05:28:25 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at lipwig.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346436AbjLLN2K (ORCPT + 99 others); Tue, 12 Dec 2023 08:28:10 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39632 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232783AbjLLN1y (ORCPT ); Tue, 12 Dec 2023 08:27:54 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7AED0F2 for ; Tue, 12 Dec 2023 05:27:59 -0800 (PST) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A46B0C433C7; Tue, 12 Dec 2023 13:27:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1702387679; bh=A61JJ3QepchMq+n/hTd5+pCDDReFj7GC3GGL0Fy/B70=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fZ79lRiYpPFSifS88bmIdqzYMk2u9yJzTZ5YDjGKQAqeIPuFqi/cUykVzdEfjJEr3 HGwBR/huZUCDaNiSo0MGDAD81Ts8ow3RgoZFHWRlw3aZQRuocakNw+aMmvegaVGTKx eCr3i+xwKcY4TWNbnJjGU+s5l3k5y1UTYCtURVICdIBlHYqK5gJvrnh7Uu3baVCuSa C6RZTGXf1ZawGLX0fbo938bWA/f+MykhCONd22BJqfbdvcKMm0rv337CLe37x3siRD Wf6RsIxZoGePOPoXScTnQyiMPFSi7j6n8ju05rhVmxYq9/HVyQX4IhO8K/rLeTmVxY 38iOk+lm6bzIA== Date: Tue, 12 Dec 2023 14:27:56 +0100 From: Frederic Weisbecker To: Gianfranco Dutka Cc: Waiman Long , Tejun Heo , Vincent Guittot , linux-kernel@vger.kernel.org, vincent.guittot@linaro.com, Ingo Molnar , Peter Zijlstra , Juri Lelli , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Daniel Bristot de Oliveira , Valentin Schneider , "Pandruvada, Srinivas" Subject: Re: Modifying isolcpus, nohz_full, and rcu_nocb kernel parameters at runtime Message-ID: References: <76587DD3-2A77-41A3-9807-6AEE4398EBA6@arista.com> <25E6E1E4-DC16-490E-B907-A3236FB9317A@arista.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <25E6E1E4-DC16-490E-B907-A3236FB9317A@arista.com> X-Spam-Status: No, score=-1.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lipwig.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Tue, 12 Dec 2023 05:28:25 -0800 (PST) On Fri, Dec 08, 2023 at 09:18:53AM -0500, Gianfranco Dutka wrote: > > > The isolcpus, nohz_full and rcu_nocbs are boot-time kernel parameters. I am in the process of improving dynamic CPU isolation at runtime. Right now, we are able to do isolcpus=domain with the isolated cpuset partition functionality. Other aspects of CPU isolation are being looked at with the goal of reducing the gap of what one can do at boot time versus what can be done at run time. It will certain take time to reach that goal. > > > > Cheers, > > Longman > > > > Thank you Waiman for the response. It would seem that getting similar > functionality through cgroups/cpusets is the only option at the moment. Is it > completely out of the question to possibly patch the kernel to modify these > parameters at runtime? Or would that entail a significant change that might > not be so trivial to accomplish? For instance, the solution wouldn’t be as > simple as patching the kernel to make these writeable and then calling the > same functions which run at boot-time when these parameters are originally > written? As for nohz_full (which implies rcu_nocb), it's certainly possible to make it tunable at runtime via cpusets. If people really want it, I'm willing to help. Thanks.