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 97F29C4332F for ; Mon, 21 Nov 2022 11:42:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231393AbiKULmR (ORCPT ); Mon, 21 Nov 2022 06:42:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38252 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231497AbiKULly (ORCPT ); Mon, 21 Nov 2022 06:41:54 -0500 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 132A2AE76; Mon, 21 Nov 2022 03:41:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=5OxVIP2sJTBTWq/HDoIIRbvS+t0aPa1aRm3P4GNn+Wk=; b=H4laSJ1TRP/mfaaM4wESvfDwE9 PFHpESfJfhILhDgGrfBvGQt/qt3VCehWWLDrm+3wbzIsgaj43DnA4q4kHZ+ocqjg6PqKq1+cW5fVL +OMQXU+zdhPwvy2lgbUEFiM8B4tidtEmyesfJv4tcYq50Aknwyg4vWOvBRmPRK3SPfIZqaw7tdcuW Gmmqwf6OEDTRSF/J0YFyK5U8pRokBYunI8v+jDzUb8KnybQIPKMh4gOd7ftySOe40RF0m5kxwQg54 SGmU5+8+6TGl481N79xPo+MNFGh6LImMgNKvgAsTcGfmiGz1aunrZhGOhvPVXkyukdyBLiojt1LYq 2Vq72oTw==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=noisy.programming.kicks-ass.net) by casper.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1ox5Ay-005AXw-Rb; Mon, 21 Nov 2022 11:41:26 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id 9F7A13006A4; Mon, 21 Nov 2022 12:41:17 +0100 (CET) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 870972BE3B104; Mon, 21 Nov 2022 12:41:17 +0100 (CET) Date: Mon, 21 Nov 2022 12:41:17 +0100 From: Peter Zijlstra To: Luis Chamberlain Cc: Kefeng Wang , Ingo Molnar , Juri Lelli , Vincent Guittot , Kees Cook , Iurii Zaikin , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH] sched: Move numa_balancing sysctls to its own file Message-ID: References: <20220908072531.87916-1-wangkefeng.wang@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 08, 2022 at 05:06:03PM -0700, Luis Chamberlain wrote: > On Thu, Sep 08, 2022 at 03:25:31PM +0800, Kefeng Wang wrote: > > The sysctl_numa_balancing_promote_rate_limit and sysctl_numa_balancing > > are part of sched, move them to its own file. > > > > Signed-off-by: Kefeng Wang > > There is quite a bit of random cleanup on each kernel release > for sysctls to do things like what you just did. Because of this it has its > own tree to help avoid conflicts. Can you base your patches on the > sysctl-testing branch here and re-submit: > > https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/log/?h=sysctl-testing > > If testing goes fine, then I'd move this to sysctl-next which linux-next > picks up for yet more testing. > > Are scheduling folks OK with this patch and me picking it up on the > sysctl-next tree if all tests are a go? Yeah, think so, it just moves stuff around a bit. ACK.