public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
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 0/4] preparation for zcrx with huge pages
Date: Tue, 22 Apr 2025 15:44:40 +0100	[thread overview]
Message-ID: <cover.1745328503.git.asml.silence@gmail.com> (raw)

Add barebone support for huge pages for zcrx, with the only real
effect is shrinking the page array. However, it's a prerequisite
for other huge page optimisations, like improved dma mappings and
large page pool allocation sizes.

There is no new uapi, but there is a basic example:

https://github.com/isilence/liburing/tree/zcrx-huge-page

Pavel Begunkov (4):
  io_uring/zcrx: add helper for importing user memory
  io_uring/zcrx: add initial infra for large pages
  io_uring: export io_coalesce_buffer()
  io_uring/zcrx: coalesce areas with huge pages

 io_uring/rsrc.c |  2 +-
 io_uring/rsrc.h |  2 ++
 io_uring/zcrx.c | 88 +++++++++++++++++++++++++++++++++++++------------
 io_uring/zcrx.h |  3 ++
 4 files changed, 73 insertions(+), 22 deletions(-)

-- 
2.48.1


             reply	other threads:[~2025-04-22 14:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 14:44 Pavel Begunkov [this message]
2025-04-22 14:44 ` [PATCH 1/4] io_uring/zcrx: add helper for importing user memory Pavel Begunkov
2025-04-22 14:44 ` [PATCH 2/4] io_uring/zcrx: add initial infra for large pages Pavel Begunkov
2025-04-22 14:44 ` [PATCH 3/4] io_uring: export io_coalesce_buffer() Pavel Begunkov
2025-04-22 14:44 ` [PATCH 4/4] io_uring/zcrx: coalesce areas with huge pages Pavel Begunkov
2025-04-25 14:01 ` [PATCH 0/4] preparation for zcrx " Pavel Begunkov
2025-04-25 15:42   ` David Wei
2025-04-26  0:01     ` 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.1745328503.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