diff options
author | David Wei <dw@davidwei.uk> | 2025-02-24 07:13:18 +0300 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2025-02-24 22:55:58 +0300 |
commit | 6699ec9a23f85f1764183430209c741847c45f12 (patch) | |
tree | 5d511cfcbffe1ae674a5e4000d7a68d67a5ad3ec /tools/perf/scripts/python/mem-phys-addr.py | |
parent | 92ade52f26555f15880b42405e35f0cfbb8ea7db (diff) | |
download | linux-6699ec9a23f85f1764183430209c741847c45f12.tar.xz |
io_uring/zcrx: add a read limit to recvzc requests
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.
Data will still be posted in aux completions, as before. This could be
split across multiple frags. But the primary recvzc request will now
complete once N bytes have been read. The completion of the recvzc
request will have res and cflags both set to 0.
Signed-off-by: David Wei <dw@davidwei.uk>
Reviewed-by: Pavel Begunkov <asml.silence@gmail.com>
Link: https://lore.kernel.org/r/20250224041319.2389785-2-dw@davidwei.uk
[axboe: fixup io_zcrx_recv() for !CONFIG_NET]
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions