From: Xavier <xavier_qy@163.com>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, vschneid@redhat.com,
linux-kernel@vger.kernel.org, oliver.sang@intel.com
Subject: Re:Re: [PATCH-RT sched v3 0/2] Optimize the RT group scheduling
Date: Tue, 16 Jul 2024 17:17:50 +0800 (CST) [thread overview]
Message-ID: <6af6feef.83df.190bad579d3.Coremail.xavier_qy@163.com> (raw)
In-Reply-To: <20240716085926.GP14400@noisy.programming.kicks-ass.net>
Hi Peter,
Your meaning is, will the RT scheduling policy be removed? I see that the
current kernel already includes the deadline and EEVDF scheduling policies.
I noticed that the enqueue and dequeue operations for RT are quite
complicated, so I proposed this patch for optimization.
At 2024-07-16 16:59:26, "Peter Zijlstra" <peterz@infradead.org> wrote:
>On Tue, Jul 16, 2024 at 01:25:41PM +0800, Xavier wrote:
>> Hi all,
>>
>> Patch 3 fixed the issue with handling tasks with prio set to 0 during
>> the execution of blktests.
>
>*sigh*... are you actually using this horror show?
>
>The plan was to scrap this code -- and replace it with something based
>on deadline servers. Sadly not a lot of people are able to work on that
>:/
next prev parent reply other threads:[~2024-07-16 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 5:25 [PATCH-RT sched v3 0/2] Optimize the RT group scheduling Xavier
2024-07-16 5:25 ` [PATCH-RT sched v3 1/2] RT SCHED: Optimize the enqueue and dequeue operations for rt_se Xavier
2024-07-16 5:25 ` [PATCH-RT sched v3 2/2] RT test: Adding test cases for RT group scheduling Xavier
2024-07-16 8:59 ` [PATCH-RT sched v3 0/2] Optimize the " Peter Zijlstra
2024-07-16 9:17 ` Xavier [this message]
2024-07-16 10:25 ` 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=6af6feef.83df.190bad579d3.Coremail.xavier_qy@163.com \
--to=xavier_qy@163.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox