From: Hillf Danton <hdanton@sina.com>
To: Qais Yousef <qais.yousef@arm.com>
Cc: John Stultz <jstultz@google.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Connor O'Brien <connoro@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [RFC PATCH v4 2/3] sched: Avoid placing RT threads on cores handling long softirqs
Date: Tue, 11 Oct 2022 19:18:46 +0800 [thread overview]
Message-ID: <20221011111846.284-1-hdanton@sina.com> (raw)
In-Reply-To: <20221010154216.6mw7fszdaoajurvm@wubuntu>
On 10 Oct 2022 16:42:16 +0100 Qais Yousef <qais.yousef@arm.com>
> On 10/05/22 14:01, Hillf Danton wrote:
> > On 4 Oct 2022 18:13:52 -0700 John Stultz <jstultz@google.com>
> > > On Tue, Oct 4, 2022 at 5:22 PM Hillf Danton <hdanton@sina.com> wrote:
> > > > On 3 Oct 2022 19:29:36 -0700 John Stultz <jstultz@google.com>
> > > > >
> > > > > Why would ksoftirqd preempt the rt task?
> > > > >
> > > > For example the kthread becomes sensitive to latency.
> > >
> > > Is it the case where
> > > the ksoftirqd thread is configured to run at higher rtprio?
> > >
> > Yes, you are right.
>
> I don't see a problem here. If a sys-admin configures their ksoftirqds to be
> a higher priority RT tasks than the audio threads, then they better know what
> they're doing :-)
>
Thanks for taking a look.
> The issue at hand here is that the softirqs boundedness is hard to control. And
> the scheduling delays ensued are hard to deal with by any sys-admin.
>
Given "The RT scheduler is for tasks that require strick scheduling
requirements over all else, including performance." [1], I would invite
Steve to shed some more light on the relation between RT scheduler and
performance/network throughputs.
Bonus question, why softirq took no care of RT tasks, given strick
scheduling requirements above?
[1] https://lore.kernel.org/lkml/257E96C2-6ABD-4DD6-9B7F-771DA3D1BAAA@goodmis.org/
> Networking has actually introduced some knobs to help control that - but the
> tricky bit of still being able to deliver high throughput networking while
> keeping the softirq bounded to minimize scheduling delays/latencies. I think
> even for PREEMPT_RT, high performance networking could be impacted to achieve
> the required low latency.
>
> See this paper which explores this duality:
>
> https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.702.7571&rep=rep1&type=pdf
>
>
> With WiFi 6 and 5G mobile networks, phones are actually expected to deliver
> multi-gigabit network throughputs.
next prev parent reply other threads:[~2022-10-11 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221003232033.3404802-3-jstultz@google.com>
2022-10-04 1:36 ` Hillf Danton
2022-10-04 2:29 ` John Stultz
2022-10-05 0:21 ` Hillf Danton
2022-10-05 1:13 ` John Stultz
2022-10-05 6:01 ` Hillf Danton
2022-10-10 15:42 ` Qais Yousef
2022-10-11 11:18 ` Hillf Danton [this message]
2022-10-12 14:10 ` Qais Yousef
2022-10-13 1:43 ` Hillf Danton
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=20221011111846.284-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=connoro@google.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=rostedt@goodmis.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