From: Jakub Kicinski <kuba@kernel.org>
To: Adrien Thierry <athierry@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/net: give more time to udpgro bg processes to complete startup
Date: Thu, 3 Nov 2022 20:46:07 -0700 [thread overview]
Message-ID: <20221103204607.520b36ac@kernel.org> (raw)
In-Reply-To: <20221101184809.50013-1-athierry@redhat.com>
On Tue, 1 Nov 2022 14:48:08 -0400 Adrien Thierry wrote:
> In some conditions, background processes in udpgro don't have enough
> time to set up the sockets. When foreground processes start, this
> results in the test failing with "./udpgso_bench_tx: sendmsg: Connection
> refused". For instance, this happens from time to time on a Qualcomm
> SA8540P SoC running CentOS Stream 9.
>
> To fix this, increase the time given to background processes to
> complete the startup before foreground processes start.
>
> Signed-off-by: Adrien Thierry <athierry@redhat.com>
> ---
> This is a continuation of the hack that's present in those tests. Other
> ideas are welcome to fix this in a more permanent way.
Perhaps we can add an option to the Rx side to daemonize itself after
setting up the socket, that way the bash script will be locked until
Rx is ready?
next prev parent reply other threads:[~2022-11-04 3:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 18:48 [PATCH] selftests/net: give more time to udpgro bg processes to complete startup Adrien Thierry
2022-11-04 3:46 ` Jakub Kicinski [this message]
2022-11-04 8:54 ` Paolo Abeni
2022-11-04 17:47 ` Jakub Kicinski
2022-11-04 10:20 ` patchwork-bot+netdevbpf
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=20221103204607.520b36ac@kernel.org \
--to=kuba@kernel.org \
--cc=athierry@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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).