On 2/24/25 1:33 PM, David Wei wrote: > On 2025-02-24 11:56, Jens Axboe wrote: >> 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. >> > > Thanks, and sorry for the noise. I'll be sure to compile check > !CONFIG_NET next time. Easy to miss, and the kernel test bot always finds them. So not a huge deal. -- Jens Axboe
