From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: axboe@kernel.dk, netdev@vger.kernel.org
Subject: Re: [PATCH io_uring-7.1 0/4] follow up zcrx fixes
Date: Wed, 25 Mar 2026 12:14:08 +0000 [thread overview]
Message-ID: <3aa1fb50-3a19-403e-99da-b8a12fa54104@gmail.com> (raw)
In-Reply-To: <cover.1774439286.git.asml.silence@gmail.com>
On 3/25/26 12:08, Pavel Begunkov wrote:
> Follow up fixes for the recent update flagged by review.
Actually, I'm not happy how it interacts with the nodev mode,
I'll send a v2
--
Pavel Begunkov
prev parent reply other threads:[~2026-03-25 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 12:08 [PATCH io_uring-7.1 0/4] follow up zcrx fixes Pavel Begunkov
2026-03-25 12:08 ` [PATCH io_uring-7.1 1/4] io_uring/zcrx: don't use mark0 for allocating xarray Pavel Begunkov
2026-03-25 12:08 ` [PATCH io_uring-7.1 2/4] io_uring/zcrx: don't clear not allocated niovs Pavel Begunkov
2026-03-25 12:08 ` [PATCH io_uring-7.1 3/4] io_uring/zcrx: use dma_len for chunk size calculation Pavel Begunkov
2026-03-25 12:08 ` [PATCH io_uring-7.1 4/4] io_uring/zcrx: use correct mmap off constants Pavel Begunkov
2026-03-25 12:14 ` Pavel Begunkov [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 \
--in-reply-to=3aa1fb50-3a19-403e-99da-b8a12fa54104@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=netdev@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