linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Zhen Ni <nizhen@uniontech.com>,
	mingo@redhat.com, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, keescook@chromium.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] sched: move rr_timeslice sysctls to rt.c
Date: Fri, 11 Feb 2022 10:23:42 -0800	[thread overview]
Message-ID: <YgaprpOvUYlrNvdH@bombadil.infradead.org> (raw)
In-Reply-To: <20220211115114.GU23216@worktop.programming.kicks-ass.net>

Cc'ing Andrew for coordination on merging these sorts of patches.

On Fri, Feb 11, 2022 at 12:51:14PM +0100, Peter Zijlstra wrote:
> So I've dropped the whole lot I had:
> 
> patches/zhen_ni-sched-move_energy_aware_sysctls_to_topology_c.patch
> patches/zhen_ni-sched-move_cfs_bandwidth_slice_sysctls_to_fair_c.patch
> patches/zhen_ni-sched-move_uclamp_util_sysctls_to_core_c.patch
> patches/zhen_ni-sched-move_schedstats_sysctls_to_core_c.patch
> patches/zhen_ni-sched-move_deadline_period_sysctls_to_deadline_c.patch
> patches/zhen_ni-sched-move_rt_period_runtime_sysctls_to_rt_c.patch
> patches/zhen_ni-sched-move_rr_timeslice_sysctls_to_rt_c.patch
> 
> And I expect a single coherent series or I'll forgo all this.

I suspect Zhen will follow up accordingly.

So Andrew had merged tons of initial cleanups for kernel/sysctl.c. Now
that some of the initial grunt work and sysctls for fs are out of
kernel/sysctl.c, I'm seeing the next target seems to be the scheduler. I
don't think these *need* to go through Andrew's tree since the fs
changes are already on Linus' tree. So figured I'd drop this note to
just remind ourselves that if accumulate a few of these patches for one
subsystem there is a greater risk of a conflict later with another
subsystem doing some similar cleanup. So for the next release I think it
makes sense to keep this localized somehow if we can. Maybe we just deal
with these on Peter's tree?

  Luis

      reply	other threads:[~2022-02-11 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  6:08 [PATCH] sched: move rr_timeslice sysctls to rt.c Zhen Ni
2022-02-11 11:51 ` Peter Zijlstra
2022-02-11 18:23   ` Luis Chamberlain [this message]

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=YgaprpOvUYlrNvdH@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=nizhen@uniontech.com \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.org \
    /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).