From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com, David Wei <dw@davidwei.uk>
Subject: [PATCH liburing 0/2] add zcrx example
Date: Wed, 9 Apr 2025 18:58:34 +0100 [thread overview]
Message-ID: <cover.1744221361.git.asml.silence@gmail.com> (raw)
We need a simple example for zcrx to show case how the api works
and how to use features. Take the selftest and strip it off tx.
Anything supporting tcp can play a role of the sender, but for
data verification (-v) it needs to follow the data pattern.
Implement it in send-zerocopy -z0.
Pavel Begunkov (2):
examples/send-zerocopy: add data verification
examples: add a zcrx example
examples/Makefile | 1 +
examples/send-zerocopy.c | 50 +++++-
examples/zcrx.c | 362 +++++++++++++++++++++++++++++++++++++++
3 files changed, 410 insertions(+), 3 deletions(-)
create mode 100644 examples/zcrx.c
--
2.48.1
next reply other threads:[~2025-04-09 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 17:58 Pavel Begunkov [this message]
2025-04-09 17:58 ` [PATCH liburing 1/2] examples/send-zerocopy: add data verification Pavel Begunkov
2025-04-09 17:58 ` [PATCH liburing 2/2] examples: add a zcrx example Pavel Begunkov
2025-04-09 23:00 ` Pavel Begunkov
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 \
--in-reply-to=cover.1744221361.git.asml.silence@gmail.com \
--to=asml.silence@gmail.com \
--cc=dw@davidwei.uk \
--cc=io-uring@vger.kernel.org \
/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