From: Hillf Danton <hdanton@sina.com>
To: John Stultz <jstultz@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, "Connor O'Brien" <connoro@google.com>,
Qais Yousef <qais.yousef@arm.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: Wed, 5 Oct 2022 08:21:49 +0800 [thread overview]
Message-ID: <20221005002149.1876-1-hdanton@sina.com> (raw)
In-Reply-To: <CANDhNCoVzJ_MSyAigMkE-TMgfRQRkiK=G0_S3OwPfnXPuKu1iA@mail.gmail.com>
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.
next prev parent reply other threads:[~2022-10-05 0:22 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 [this message]
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
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=20221005002149.1876-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