From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Cc: dw@davidwei.uk
Subject: Re: [PATCH v2 0/3] account zcrx area pinned memory
Date: Fri, 18 Jul 2025 15:18:14 -0600 [thread overview]
Message-ID: <430975c6-6814-4683-b4f1-c05695c1e551@kernel.dk> (raw)
In-Reply-To: <ed4fcb1c-795c-4af2-bb47-7c6bd5c438cf@gmail.com>
On 7/18/25 1:01 PM, Pavel Begunkov wrote:
> On 7/18/25 19:59, Pavel Begunkov wrote:
>> Honour RLIMIT_MEMLOCK while pinning zcrx areas.
>
> It appeared cleaner resending the whole thing. Let me know
> if a fixup patch is preferable.
Fixup would be better in this case, as there's already other
patches on top at this point.
--
Jens Axboe
prev parent reply other threads:[~2025-07-18 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 18:59 [PATCH v2 0/3] account zcrx area pinned memory Pavel Begunkov
2025-07-18 18:59 ` [PATCH v2 1/3] io_uring: export io_[un]account_mem Pavel Begunkov
2025-07-18 18:59 ` [PATCH v2 2/3] io_uring/zcrx: account area memory Pavel Begunkov
2025-07-18 18:59 ` [PATCH v2 3/3] io_uring/zcrx: fix leaking pages on sg init fail Pavel Begunkov
2025-07-18 19:01 ` [PATCH v2 0/3] account zcrx area pinned memory Pavel Begunkov
2025-07-18 21:18 ` Jens Axboe [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=430975c6-6814-4683-b4f1-c05695c1e551@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