From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Kees Cook <keescook@chromium.org>,
Iurii Zaikin <yzaikin@google.com>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] sched: Move numa_balancing sysctls to its own file
Date: Fri, 9 Sep 2022 09:46:21 +0800 [thread overview]
Message-ID: <679d8f0c-f8cc-d43e-5467-c32a78bcb850@huawei.com> (raw)
In-Reply-To: <YxqDa+WALRr8L7Q8@bombadil.infradead.org>
On 2022/9/9 8:06, 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 <wangkefeng.wang@huawei.com>
> 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:
Found this when reading memory tiering code，sure to re-submit based your
branch,
thanks.
>
> 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?
>
> Luis
> .
next prev parent reply other threads:[~2022-09-09 1:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 7:25 [PATCH] sched: Move numa_balancing sysctls to its own file Kefeng Wang
2022-09-08 12:07 ` [PATCH Resend] " Kefeng Wang
2022-09-09 0:06 ` [PATCH] " Luis Chamberlain
2022-09-09 1:46 ` Kefeng Wang [this message]
2022-09-09 3:37 ` Kefeng Wang
2022-09-09 19:44 ` Luis Chamberlain
2022-09-13 8:39 ` Kefeng Wang
2022-11-21 3:09 ` Kefeng Wang
2022-11-21 4:58 ` Luis Chamberlain
2022-11-21 8:20 ` Kefeng Wang
2022-11-21 11:41 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=679d8f0c-f8cc-d43e-5467-c32a78bcb850@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=yzaikin@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).