From: David Wei <dw@davidwei.uk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH v4 0/6] zcrx huge pages support Vol 1
Date: Wed, 2 Jul 2025 16:12:19 -0700 [thread overview]
Message-ID: <01e5a711-fe8b-4d5c-b8c6-325fe2d67dff@davidwei.uk> (raw)
In-Reply-To: <cover.1751466461.git.asml.silence@gmail.com>
On 2025-07-02 07:29, Pavel Begunkov wrote:
> Use sgtable as the common format b/w dmabuf and user pages, deduplicate
> dma address propagation handling, and use it to omptimise dma mappings.
> It also prepares it for larger size for NIC pages.
>
> v4: further restrict kmap fallback length, v3 isn't be generic
> enough to cover future uses.
>
> v3: truncate kmap'ed length by both pages
>
> v2: Don't coalesce into folios, just use sg_alloc_table_from_pages()
> for now. Coalescing will return back later.
>
> Improve some fallback copy code. Patch 1, and Patch 6 adding a
> helper to work with larger pages, which also allows to get rid
> of skb_frag_foreach_page.
>
> Return copy fallback helpers back to pages instead of folios,
> the latter wouldn't be correct in all cases.
>
> Pavel Begunkov (6):
> io_uring/zcrx: always pass page to io_zcrx_copy_chunk
> io_uring/zcrx: return error from io_zcrx_map_area_*
> io_uring/zcrx: introduce io_populate_area_dma
> io_uring/zcrx: allocate sgtable for umem areas
> io_uring/zcrx: assert area type in io_zcrx_iov_page
> io_uring/zcrx: prepare fallback for larger pages
>
> io_uring/zcrx.c | 241 +++++++++++++++++++++++++-----------------------
> io_uring/zcrx.h | 1 +
> 2 files changed, 128 insertions(+), 114 deletions(-)
>
What did you use to test this patch series or will that come with vol 2?
next prev parent reply other threads:[~2025-07-02 23:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 14:29 [PATCH v4 0/6] zcrx huge pages support Vol 1 Pavel Begunkov
2025-07-02 14:29 ` [PATCH v4 1/6] io_uring/zcrx: always pass page to io_zcrx_copy_chunk Pavel Begunkov
2025-07-02 22:32 ` David Wei
2025-07-02 14:29 ` [PATCH v4 2/6] io_uring/zcrx: return error from io_zcrx_map_area_* Pavel Begunkov
2025-07-02 22:27 ` David Wei
2025-07-02 22:50 ` Pavel Begunkov
2025-07-02 23:20 ` David Wei
2025-07-02 14:29 ` [PATCH v4 3/6] io_uring/zcrx: introduce io_populate_area_dma Pavel Begunkov
2025-07-02 23:13 ` David Wei
2025-07-02 14:29 ` [PATCH v4 4/6] io_uring/zcrx: allocate sgtable for umem areas Pavel Begunkov
2025-07-02 23:16 ` David Wei
2025-07-02 14:29 ` [PATCH v4 5/6] io_uring/zcrx: assert area type in io_zcrx_iov_page Pavel Begunkov
2025-07-02 14:29 ` [PATCH v4 6/6] io_uring/zcrx: prepare fallback for larger pages Pavel Begunkov
2025-07-02 23:12 ` David Wei [this message]
2025-07-02 23:51 ` [PATCH v4 0/6] zcrx huge pages support Vol 1 Pavel Begunkov
2025-07-08 18:00 ` Jens Axboe
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=01e5a711-fe8b-4d5c-b8c6-325fe2d67dff@davidwei.uk \
--to=dw@davidwei.uk \
--cc=asml.silence@gmail.com \
--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