Messages in this thread | | | From | Alexandru Ardelean <> | Date | Wed, 17 Apr 2024 09:48:36 +0300 | Subject | Re: [PATCH][V2] sched/rt: Print curr when RT throttling activated |
| |
On Mon, Apr 8, 2024 at 6:25 PM Valentin Schneider <vschneid@redhat.com> wrote: > > 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/
Ah. Thanks for the input :) I'll shut up on this.
Thanks Alex
>
| |