[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <qshy7xf5pzgabrbvioe7v5tz45etzk22r3t3phklrnkq7tn6hs@3kv76yk73afl>
Date: Thu, 20 Nov 2025 02:03:44 -0800
From: Breno Leitao <leitao@...ian.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
willemdebruijn.kernel@...il.com, shuah@...nel.org, sdf@...ichev.me, krakauer@...gle.com,
linux-kselftest@...r.kernel.org, petrm@...dia.com, matttbe@...nel.org,
Willem de Bruijn <willemb@...gle.com>
Subject: Re: [PATCH net-next v3 06/12] selftests: net: py: support ksft ready
without wait
On Wed, Nov 19, 2025 at 06:10:18PM -0800, Jakub Kicinski wrote:
> There's a common synchronization problem when a script (Python test)
> uses a C program to set up some state (usually start a receiving
> process for traffic). The script needs to know when the process
> has fully initialized. The inverse of the problem exists for shutting
> the process down - we need a reliable way to tell the process to exit.
>
> We added helpers to do this safely in
> commit 71477137994f ("selftests: drv-net: add a way to wait for a local process")
> unfortunately the two operations (wait for init, and shutdown) are
> controlled by a single parameter (ksft_wait). Add support for using
> ksft_ready without using the second fd for exit.
>
> This is useful for programs which wait for a specific number of packets
> to rx so exit_wait is a good match, but we still need to wait for init.
>
> Reviewed-by: Petr Machata <petrm@...dia.com>
> Reviewed-by: Willem de Bruijn <willemb@...gle.com>
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
Reviewed-by: breno Leitao <leitao@...ian.org>
Powered by blists - more mailing lists