From: Ankit Jain <ankitja@vmware.com>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: "srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Sharan Turlapati <sturlapati@vmware.com>,
Him Kalyan Bordoloi <bordoloih@vmware.com>,
Keerthana Kalyanasundaram <keerthanak@vmware.com>,
Anish Swaminathan <anishs@vmware.com>,
Srivatsa Bhat <srivatsab@vmware.com>
Subject: Re: [PATCH] sched/deadline: Fix BUG_ON condition for deboosted tasks
Date: Tue, 19 Jul 2022 05:30:16 +0000 [thread overview]
Message-ID: <B466E709-EFCF-4B27-B3F6-D7561C381BF7@vmware.com> (raw)
In-Reply-To: <YtVZokpe+l50EpWs@localhost.localdomain>
> On 18-Jul-2022, at 6:31 PM, Juri Lelli <juri.lelli@redhat.com> wrote:
>
> ⚠ External Email
>
> On 18/07/22 07:46, Ankit Jain wrote:
>
> ...
>
>> Hi Juri,
>>
>> Actually, while testing I already included below commits in 4.19-rt :
>>
>> feff2e65efd8d84cf831668e182b2ce73c604bbb (sched/deadline: Unthrottle PI boosted threads while
>> enqueuing)
>> 46fcc4b00c3cca8adb9b7c9afdd499f64e427135 (sched/deadline: Fix stale throttling on de-/boosted tasks)
>> 2279f540ea7d05f22d2f0c4224319330228586bc (sched/deadline: Fix priority inheritance with multiple)
>> 0e3872499de1a1230cef5221607d71aa09264bd5 (kernel/sched: Remove dl_boosted flag comment)
>
> Interesting.
>
> Is the workload you are using to test this easily reproducible? I'd like
> to try that out on my end to check if I see the same (of course the
> issue I was working on goes away with my fix :).
>
> Best,
> Juri
>
Hi Juri,
The test with which i am able to hit the issue is as follows:
• Schedule SCHED_FIFO/55 (sched_priority = 55) tasks running infinite loop on all isolated cores.
• spwan 30-40 docker containers in loop (docker load , docker run)
• Immediately after that schedule SCHED_FIFO/55 (sched_priority = 55) tasks running infinite loop on all isolated cores again.
• BUG_ON gets hit almost every time.
System config as follows:
• 4.19-rt kernel
• 40 cpu (0-1 housekeeping, 2-39 isol cpus)
• stalld-1.3.0 with the fixes from latest version (for task starvation avoidance), "tuned" with real-time profile
Thanks.
next prev parent reply other threads:[~2022-07-19 5:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 7:50 Juri Lelli
2022-07-13 11:46 ` Peter Zijlstra
2022-07-13 12:58 ` Juri Lelli
2022-07-13 21:31 ` Srivatsa S. Bhat
2022-07-14 7:28 ` Juri Lelli
2022-07-15 4:49 ` Ankit Jain
2022-07-15 7:47 ` Juri Lelli
2022-07-18 7:46 ` Ankit Jain
2022-07-18 13:01 ` Juri Lelli
2022-07-19 5:30 ` Ankit Jain [this message]
2022-07-19 7:19 ` Juri Lelli
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=B466E709-EFCF-4B27-B3F6-D7561C381BF7@vmware.com \
--to=ankitja@vmware.com \
--cc=anishs@vmware.com \
--cc=bordoloih@vmware.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=keerthanak@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=sturlapati@vmware.com \
--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
all inboxes | Powered by JetHome®