From: Valentin Schneider <vschneid@redhat.com>
To: Alexandru Ardelean <alex@shruggie.ro>, linux-kernel@vger.kernel.org
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, tian.xianting@h3c.com,
steffen.aschbacher@stihl.de, gregkh@linuxfoundation.org
Subject: Re: [PATCH][V2] sched/rt: Print curr when RT throttling activated
Date: Mon, 08 Apr 2024 17:25:50 +0200 [thread overview]
Message-ID: <xhsmho7ajanb5.mognet@vschneid-thinkpadt14sgen2i.remote.csb> (raw)
In-Reply-To: <CAH3L5QqZ61H9Fk24R4K3vNdpmvBjnxHaxH7CRTT5Fa3tbot_hg@mail.gmail.com>
On 01/04/24 18:47, Alexandru Ardelean wrote:
> On Thu, Jul 13, 2023 at 11:07 PM Alexandru Ardelean <alex@shruggie.ro> wrote:
>>
>> On Tue, May 16, 2023 at 3:22 PM Alexandru Ardelean <alex@shruggie.ro> wrote:
>> >
>> > From: Xianting Tian <tian.xianting@h3c.com>
>> >
>> > We may meet the issue, that one RT thread occupied the cpu by 950ms/1s,
>> > The RT thread maybe is a business thread or other unknown thread.
>> >
>> > Currently, it only outputs the print "sched: RT throttling activated"
>> > when RT throttling happen. It is hard to know what is the RT thread,
>> > For further analysis, we need add more prints.
>> >
>> > This patch is to print current RT task when RT throttling activated,
>> > It help us to know what is the RT thread in the first time.
>> >
>>
>> Adding Greg on this patch, since it 's been a while.
>> And also: ping :)
>
> Ping on this :)
>
AFAIA this has been proposed a few times in the past, the problem is that
printing the current task isn't the right thing to do as it may not be the
one that contributed most of the runtime that lead to throttling.
See https://lore.kernel.org/lkml/20221209163606.53a2370e@gandalf.local.home/
next prev parent reply other threads:[~2024-04-08 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 12:22 Alexandru Ardelean
2023-07-13 20:07 ` Alexandru Ardelean
2024-04-01 15:47 ` Alexandru Ardelean
2024-04-08 15:25 ` Valentin Schneider [this message]
2024-04-17 6:48 ` Alexandru Ardelean
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=xhsmho7ajanb5.mognet@vschneid-thinkpadt14sgen2i.remote.csb \
--to=vschneid@redhat.com \
--cc=alex@shruggie.ro \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--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=steffen.aschbacher@stihl.de \
--cc=tian.xianting@h3c.com \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®