From: Jakub Kicinski <kuba@kernel.org>
To: David Wei <dw@davidwei.uk>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
jdamato@fastly.com, asml.silence@gmail.com,
io-uring@vger.kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] selftests: drv-net: iou-zcrx: wait for memory provider cleanup
Date: Mon, 2 Mar 2026 16:46:42 -0800 [thread overview]
Message-ID: <20260302164642.43375391@kernel.org> (raw)
In-Reply-To: <8489fcbf-ab76-48a9-a21f-d7f6873b9a2f@davidwei.uk>
On Mon, 2 Mar 2026 07:49:01 -0800 David Wei wrote:
> > +def mp_clear_wait(cfg):
> > + """Wait for io_uring memory providers to clear from all device queues."""
> > + deadline = time.time() + 5
>
> This is potentially a very long time to wait if code is buggy, as I
> found out when debugging netkit queue lease. How about reducing this to
> say 1 second?
Just to be clear -- you're saying that 5 seconds is a long time to wait?
Please note that if this wait times out we're going to fail the test,
the timeout does not impact the length of a successful run.
I picked 5 sec because with all the debugs enabled and under QEMU
scheduling latency spikes can be pretty brutal. I guess I could make it
3 seconds if it matters a lot?
next prev parent reply other threads:[~2026-03-03 0:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 17:13 [PATCH net-next 0/3] selftests: drv-net: iou-zcrx: improve stability and make the large chunk test work Jakub Kicinski
2026-02-27 17:13 ` [PATCH net-next 1/3] selftests: drv-net: iou-zcrx: wait for memory provider cleanup Jakub Kicinski
2026-03-02 15:32 ` Dragos Tatulea
2026-03-02 15:49 ` David Wei
2026-03-03 0:46 ` Jakub Kicinski [this message]
2026-03-03 1:39 ` David Wei
2026-02-27 17:13 ` [PATCH net-next 2/3] selftests: drv-net: iou-zcrx: rework large chunks test to use common setup Jakub Kicinski
2026-03-02 15:54 ` David Wei
2026-03-03 0:48 ` Jakub Kicinski
2026-03-03 1:44 ` David Wei
2026-02-27 17:13 ` [PATCH net-next 3/3] selftests: drv-net: iou-zcrx: allocate hugepages for large chunks test Jakub Kicinski
2026-03-02 15:16 ` Dragos Tatulea
2026-03-03 2:22 ` Jakub Kicinski
2026-03-03 8:41 ` Dragos Tatulea
2026-03-03 4:47 ` [PATCH net-next 0/3] selftests: drv-net: iou-zcrx: improve stability and make the large chunk test work 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=20260302164642.43375391@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=jdamato@fastly.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