From: Jens Axboe <[email protected]>
To: [email protected], David Wei <[email protected]>
Cc: Pavel Begunkov <[email protected]>, lizetao <[email protected]>
Subject: Re: [PATCH v3 0/2] io_uring/zcrx: recvzc read limit
Date: Mon, 24 Feb 2025 12:56:47 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/24/25 7:35 AM, Jens Axboe wrote:
>
> On Sun, 23 Feb 2025 20:13:17 -0800, David Wei wrote:
>> Currently multishot recvzc requests have no read limit and will remain
>> active so as long as the socket remains open. But, there are sometimes a
>> need to do a fixed length read e.g. peeking at some data in the socket.
>>
>> Add a length limit to recvzc requests `len`. A value of 0 means no limit
>> which is the previous behaviour. A positive value N specifies how many
>> bytes to read from the socket.
>>
>> [...]
>
> Applied, thanks!
>
> [1/2] io_uring/zcrx: add a read limit to recvzc requests
> commit: 9a53ea6aa5c87fe4c49297158e7982dbe4f96227
> [2/2] io_uring/zcrx: add selftest case for recvzc with read limit
> commit: f4b4948fb824a9fbaff906d96f6d575305842efc
Fixed up 1/2 for !CONFIG_NET, fwiw.
--
Jens Axboe
next prev parent reply other threads:[~2025-02-24 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 4:13 [PATCH v3 0/2] io_uring/zcrx: recvzc read limit David Wei
2025-02-24 4:13 ` [PATCH v3 1/2] io_uring/zcrx: add a read limit to recvzc requests David Wei
2025-02-24 13:11 ` Pavel Begunkov
2025-02-24 15:46 ` David Wei
2025-02-24 4:13 ` [PATCH v3 2/2] io_uring/zcrx: add selftest case for recvzc with read limit David Wei
2025-02-24 14:35 ` [PATCH v3 0/2] io_uring/zcrx: recvzc " Jens Axboe
2025-02-24 19:56 ` Jens Axboe [this message]
2025-02-24 20:33 ` David Wei
2025-02-24 22:38 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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