Message ID | 20250215041857.2108684-1-dw@davidwei.uk (mailing list archive) |
---|---|
Headers | show |
Series | add basic zero copy receive support | expand |
On 2/14/25 9:18 PM, David Wei wrote: > Add basic support for io_uring zero copy receive in liburing. Besides > the mandatory syncing of necessary liburing.h headers, add a thin > wrapper around the registration op and a unit test. > > Users still need to setup by hand e.g. mmap, setup the registration > structs, do the registration and then setup the refill queue struct > io_uring_zcrx_rq. > > In the future, I'll add code to hide the implementation details. But for > now, this unblocks the kernel selftest. man pages coming for this too?
On 2025-02-18 09:01, Jens Axboe wrote: > On 2/14/25 9:18 PM, David Wei wrote: >> Add basic support for io_uring zero copy receive in liburing. Besides >> the mandatory syncing of necessary liburing.h headers, add a thin >> wrapper around the registration op and a unit test. >> >> Users still need to setup by hand e.g. mmap, setup the registration >> structs, do the registration and then setup the refill queue struct >> io_uring_zcrx_rq. >> >> In the future, I'll add code to hide the implementation details. But for >> now, this unblocks the kernel selftest. > > man pages coming for this too? > I'm working on higher level abstractions so that users hopefully won't need to call it directly. Could I defer manpages until these take shape?
On 2/18/25 10:30 AM, David Wei wrote: > On 2025-02-18 09:01, Jens Axboe wrote: >> On 2/14/25 9:18 PM, David Wei wrote: >>> Add basic support for io_uring zero copy receive in liburing. Besides >>> the mandatory syncing of necessary liburing.h headers, add a thin >>> wrapper around the registration op and a unit test. >>> >>> Users still need to setup by hand e.g. mmap, setup the registration >>> structs, do the registration and then setup the refill queue struct >>> io_uring_zcrx_rq. >>> >>> In the future, I'll add code to hide the implementation details. But for >>> now, this unblocks the kernel selftest. >> >> man pages coming for this too? >> > > I'm working on higher level abstractions so that users hopefully won't > need to call it directly. Could I defer manpages until these take shape? Yep that's fine, thanks!