From: Jakub Kicinski <kuba@kernel.org>
To: Petr Machata <petrm@nvidia.com>
Cc: Florian Westphal <fw@strlen.de>, Simon Horman <horms@kernel.org>,
"Hangbin Liu" <liuhangbin@gmail.com>,
Jaehee Park <jhpark1013@gmail.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Ido Schimmel <idosch@nvidia.com>,
Davide Caratti <dcaratti@redhat.com>,
Matthieu Baerts <matttbe@kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [TEST] Flake report
Date: Tue, 14 May 2024 06:43:49 -0700 [thread overview]
Message-ID: <20240514064349.399ffcd7@kernel.org> (raw)
In-Reply-To: <87a5kslqk4.fsf@nvidia.com>
On Mon, 13 May 2024 18:52:25 +0200 Petr Machata wrote:
> > sch-tbf-ets-sh, sch-tbf-prio-sh
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > To: Petr Machata <petrm@nvidia.com>
> >
> > These fail way too often on non-debug kernels :(
> > Perhaps we can extend the lower bound?
>
> Hm, it sometimes goes even below -10%. It looks like we'd need to go as
> low as -15%.
A more crazy idea would be to run a low prio stress program while
the test is running. I'm guessing that perf is low because VM gets
scheduled out and doesn't get scheduled in in time. Or we can try
to increase the burst size in TBF?
next prev parent reply other threads:[~2024-05-14 13:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 23:09 [TEST] Flake report Jakub Kicinski
2024-05-10 3:24 ` Hangbin Liu
2024-05-10 8:35 ` Florian Westphal
2024-05-10 14:47 ` Jakub Kicinski
2024-05-10 16:03 ` Jakub Kicinski
2024-05-10 16:41 ` Florian Westphal
2024-05-10 18:02 ` Jakub Kicinski
2024-05-11 0:14 ` Jakub Kicinski
2024-05-11 6:50 ` Florian Westphal
2024-05-10 14:28 ` Matthieu Baerts
2024-05-30 17:35 ` Matthieu Baerts
2024-05-30 17:41 ` Jakub Kicinski
2024-05-31 7:52 ` Matthieu Baerts
2024-05-10 14:45 ` Nikolay Aleksandrov
2024-05-11 13:27 ` Simon Horman
2024-05-14 13:52 ` Aaron Conole
2024-05-13 11:58 ` Davide Caratti
2024-05-13 16:52 ` Petr Machata
2024-05-14 13:43 ` Jakub Kicinski [this message]
2024-05-21 16:29 ` Petr Machata
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=20240514064349.399ffcd7@kernel.org \
--to=kuba@kernel.org \
--cc=dcaratti@redhat.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jhpark1013@gmail.com \
--cc=liuhangbin@gmail.com \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.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;
as well as URLs for NNTP newsgroup(s).