From: Jens Axboe <[email protected]>
To: David Wei <[email protected]>, [email protected]
Cc: Pavel Begunkov <[email protected]>
Subject: Re: [PATCH liburing v1 0/3] add basic zero copy receive support
Date: Tue, 18 Feb 2025 10:31:53 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
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!
--
Jens Axboe
prev parent reply other threads:[~2025-02-18 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 4:18 [PATCH liburing v1 0/3] add basic zero copy receive support David Wei
2025-02-15 4:18 ` [PATCH liburing v1 1/3] zcrx: sync kernel headers David Wei
2025-02-18 17:04 ` Jens Axboe
2025-02-18 17:28 ` David Wei
2025-02-15 4:18 ` [PATCH liburing v1 2/3] zcrx: add basic support David Wei
2025-02-18 17:05 ` Jens Axboe
2025-02-18 17:29 ` David Wei
2025-02-15 4:18 ` [PATCH liburing v1 3/3] zcrx: add unit test David Wei
2025-02-18 17:01 ` [PATCH liburing v1 0/3] add basic zero copy receive support Jens Axboe
2025-02-18 17:30 ` David Wei
2025-02-18 17:31 ` Jens Axboe [this message]
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] \
/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