From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] sched_football: synchronize with kickoff flag to reduce skew
Date: Fri, 5 Sep 2025 15:45:03 +0200 [thread overview]
Message-ID: <aLrpX5Cd0ljf66Yo@yuki.lan> (raw)
In-Reply-To: <CAEemH2c_26s1ojGnStAxzGHVEhbVTpM0dL3PU=Od=G90gPvnGg@mail.gmail.com>
Hi!
> Thanks, I do manually test and now almost 1/20 times fail.
> And the worth mentioning that this is not a new failure in RHEL kernels.
> Those patches since the barrier have already much improved the test
> result from RHEL side. At least from RHEL RT-kernel I didn't observe
> fail any more.
>
> So ,as long as the patch works on the SUSE kernel to resolve it's NEW
> problem,
> I think we can merge.
I got another idea meanwhile, what happens if we keep bussy loop for the
defense and add the sched_yield() only to offense and crazy fans? That
should ensure that before the kickoff the defense threads should be
hogging the available CPUs.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-09-05 13:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 10:26 [LTP] [PATCH v2] sched_football: synchronize with kickoff flag to reduce skew Li Wang via ltp
2025-09-04 11:00 ` Petr Vorel
2025-09-04 11:42 ` Cyril Hrubis
2025-09-04 13:14 ` Li Wang via ltp
2025-09-04 15:28 ` Cyril Hrubis
2025-09-05 0:54 ` Li Wang via ltp
2025-09-05 4:03 ` Li Wang via ltp
2025-09-05 6:50 ` Li Wang via ltp
2025-09-05 7:03 ` Petr Vorel
2025-09-05 7:31 ` Petr Vorel
2025-09-05 7:36 ` Li Wang via ltp
2025-09-05 9:18 ` Cyril Hrubis
2025-09-05 11:50 ` Li Wang via ltp
2025-09-05 12:32 ` Cyril Hrubis
2025-09-05 12:46 ` Petr Vorel
2025-09-06 0:58 ` Li Wang via ltp
2025-09-05 12:49 ` Li Wang via ltp
2025-09-05 13:45 ` Cyril Hrubis [this message]
2025-09-05 14:48 ` Li Wang via ltp
2025-09-04 18:26 ` Petr Vorel
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=aLrpX5Cd0ljf66Yo@yuki.lan \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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