From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>, Shuah Khan <shuah@kernel.org>,
sched-ext@lists.linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET RESEND v11 sched_ext/for-6.20] Add a deadline server for sched_ext tasks
Date: Tue, 20 Jan 2026 13:10:03 -1000 [thread overview]
Message-ID: <aXALSwggUpMBJnZu@slm.duckdns.org> (raw)
In-Reply-To: <20260120215808.188032-1-arighi@nvidia.com>
Hello,
On Tue, Jan 20, 2026 at 10:50:31PM +0100, Andrea Righi wrote:
> This is a resend of the patch set originally posted here:
> https://lore.kernel.org/all/20251217093923.1556187-1-arighi@nvidia.com/
>
> Re-sending to check whether there are any remaining objections. As
> discussed during the LPC sched_ext microconference in Tokyo, a potential
> "open issue" could be to define a better interface for configuring the
> assigned bandwidth for the DL servers (currently via debugfs). However,
> this shouldn't be a blocker and we can likely discuss this further at the
> upcoming OSPM.
>
> Tejun, if there are no further comments, I think this series can be applied
> to sched_ext/for-6.20.
Yeah, this has been pending forever. Peter, Ingo, Juri, if there aren't any
objections, would it be okay to apply these through sched_ext? Or do you
want to route deadline part through sched/core?
Thanks.
--
tejun
prev parent reply other threads:[~2026-01-20 23:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 21:50 [PATCHSET RESEND v11 sched_ext/for-6.20] Add a deadline server for sched_ext tasks Andrea Righi
2026-01-20 21:50 ` [PATCH 1/7] sched/deadline: Clear the defer params Andrea Righi
2026-01-20 21:50 ` [PATCH 2/7] sched/debug: Fix updating of ppos on server write ops Andrea Righi
2026-01-20 21:50 ` [PATCH 3/7] sched/debug: Stop and start server based on if it was active Andrea Righi
2026-01-20 21:50 ` [PATCH 4/7] sched_ext: Add a DL server for sched_ext tasks Andrea Righi
2026-01-21 12:29 ` Peter Zijlstra
2026-01-21 12:49 ` Andrea Righi
2026-01-21 15:52 ` Peter Zijlstra
2026-01-21 17:27 ` Andrea Righi
2026-01-21 12:31 ` Peter Zijlstra
2026-01-21 12:51 ` Andrea Righi
2026-01-20 22:05 ` [PATCH 5/7] sched/debug: Add support to change sched_ext server params Andrea Righi
2026-01-20 22:05 ` [PATCH 6/7] selftests/sched_ext: Add test for sched_ext dl_server Andrea Righi
2026-01-20 22:05 ` [PATCH 7/7] selftests/sched_ext: Add test for DL server total_bw consistency Andrea Righi
2026-01-20 23:10 ` Tejun Heo [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=aXALSwggUpMBJnZu@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelagnelf@nvidia.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sched-ext@lists.linux.dev \
--cc=shuah@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.