From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
linux-kernel@vger.kernel.org, sched-ext@lists.linux.dev,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH sched_ext/for-6.17 1/2] sched_ext, sched/core: Factor out struct scx_task_group
Date: Tue, 17 Jun 2025 10:50:27 +0200 [thread overview]
Message-ID: <20250617085027.GM1613376@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <aEzRVj5ha38RAEr5@slm.duckdns.org>
On Fri, Jun 13, 2025 at 03:33:10PM -1000, Tejun Heo wrote:
> From 55aa129e6add97a98340326451bdadd4c5dd3242 Mon Sep 17 00:00:00 2001
> From: Tejun Heo <tj@kernel.org>
> Date: Fri, 13 Jun 2025 15:06:47 -1000
>
> More sched_ext fields will be added to struct task_group. In preparation,
> factor out sched_ext fields into struct scx_task_group to reduce clutter in
> the common header. No functional changes.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> ---
> These two patches are on top of:
>
> + Two fix pathces pending on sched_ext/for-6.16-fixes
> http://lkml.kernel.org/r/aEyy27BecPPHDWHc@slm.duckdns.org
> http://lkml.kernel.org/r/aEyzhBAl5zkP6Ku-@slm.duckdns.org
> + tip/sched/core patchset to reorganize bandwidth control interface handling
> http://lkml.kernel.org/r/20250614012346.2358261-1-tj@kernel.org
>
> See the following git branch for the merged result:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-bandwidth-control
>
> Peter, while this touches sched.h, the change is contained to scx part and
> shouldn't cause noticeable problems for other scheduler changes. I'll carry
> this through sched_ext/for-6.17. Please let me know if there are any
> concerns.
How do you want to do this dependency on the bandwidth rework? Should I
take those patches into tip/sched/core and then you base your tree on
top of that?
next prev parent reply other threads:[~2025-06-17 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 1:33 Tejun Heo
2025-06-14 1:34 ` [PATCH sched_ext/for-6.17 2/2] sched_ext: Add support for cgroup bandwidth control interface Tejun Heo
2025-06-21 3:04 ` Tejun Heo
2025-06-17 8:50 ` Peter Zijlstra [this message]
2025-06-17 18:21 ` [PATCH sched_ext/for-6.17 1/2] sched_ext, sched/core: Factor out struct scx_task_group Tejun Heo
2025-06-20 9:44 ` 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=20250617085027.GM1613376@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=void@manifault.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
all inboxes | Powered by JetHome®