From: Luis Chamberlain <mcgrof@kernel.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
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,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] sched: Move numa_balancing sysctls to its own file
Date: Fri, 9 Sep 2022 12:44:40 -0700 [thread overview]
Message-ID: <YxuXqF63RIMstdEN@bombadil.infradead.org> (raw)
In-Reply-To: <d99630ed-0753-da9e-ab03-848b66bc3c63@huawei.com>
On Fri, Sep 09, 2022 at 11:37:41AM +0800, Kefeng Wang wrote:
>
> On 2022/9/9 9:46, Kefeng Wang wrote:
> >
> > 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
> > >
> Hi Luis,the numa_balancing_promote_rate_limit_MBps from commit 1db91dd846e0
> “memory tiering: rate limit NUMA migration throughput”only on
> linux-next(from mm repo),
>
> 1)only send sysctl_numa_balancing changes based on your branch
> or
>
> 2)queued this patch from mm repo if no objection, Cc'ed Andrew
>
> Which one do your like, or other options, thanks.
2) as that would give more testing to the new code as well. We can deal
with merge conflicts on my tree later.
Luis
next prev parent reply other threads:[~2022-09-09 19:47 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
2022-09-09 3:37 ` Kefeng Wang
2022-09-09 19:44 ` Luis Chamberlain [this message]
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=YxuXqF63RIMstdEN@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=wangkefeng.wang@huawei.com \
--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).