From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Cc: David Wei <dw@davidwei.uk>
Subject: Re: [PATCH 0/8] zcrx huge pages support Vol 1
Date: Mon, 30 Jun 2025 11:31:30 -0600 [thread overview]
Message-ID: <99fcc8c2-a721-406c-b420-decbd591d7ce@kernel.dk> (raw)
In-Reply-To: <34125872-bc2b-4b49-8331-d85587bfdb9c@gmail.com>
On 6/30/25 11:12 AM, Pavel Begunkov wrote:
> On 6/17/25 15:48, Pavel Begunkov wrote:
>> Deduplicate some umem vs dmabuf code by creating sg_table for umem areas,
>> and add huge page coalescing on top. It improves iommu mapping and
>> compacts the page array, but leaves optimising the NIC page sizes to
>> follow ups.
>
> Any comments?
I'll take a closer look tomorrow, it's on the backlog after being
away for 10 days.
--
Jens Axboe
next prev parent reply other threads:[~2025-06-30 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 14:48 [PATCH 0/8] zcrx huge pages support Vol 1 Pavel Begunkov
2025-06-17 14:48 ` [PATCH 1/8] io_uring/zcrx: return error from io_zcrx_map_area_* Pavel Begunkov
2025-06-17 14:48 ` [PATCH 2/8] io_uring/zcrx: introduce io_populate_area_dma Pavel Begunkov
2025-06-17 14:48 ` [PATCH 3/8] io_uring/zcrx: allocate sgtable for umem areas Pavel Begunkov
2025-06-17 14:48 ` [PATCH 4/8] io_uring/zcrx: assert area type in io_zcrx_iov_page Pavel Begunkov
2025-06-17 14:48 ` [PATCH 5/8] io_uring/zcrx: convert io_zcrx_iov_page to use folios Pavel Begunkov
2025-06-17 14:48 ` [PATCH 6/8] io_uring/zcrx: add infra for large pages Pavel Begunkov
2025-06-17 14:48 ` [PATCH 7/8] io_uring: export io_coalesce_buffer() Pavel Begunkov
2025-06-17 14:48 ` [PATCH 8/8] io_uring/zcrx: try to coalesce area pages Pavel Begunkov
2025-06-30 17:12 ` [PATCH 0/8] zcrx huge pages support Vol 1 Pavel Begunkov
2025-06-30 17:31 ` Jens Axboe [this message]
2025-06-30 17:44 ` 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=99fcc8c2-a721-406c-b420-decbd591d7ce@kernel.dk \
--to=axboe@kernel.dk \
--cc=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