From: Jens Axboe <axboe@kernel.dk>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: io-uring@vger.kernel.org, asml.silence@gmail.com
Subject: Re: [PATCH 1/2] io_uring: split alloc and add of overflow
Date: Fri, 16 May 2025 10:33:41 -0600 [thread overview]
Message-ID: <9bf4b0e9-df89-4f8d-8562-7122e57a47b0@kernel.dk> (raw)
In-Reply-To: <CADUfDZrp-Qq93g5uZn4_=amFhzF=j2Yk0MqJ5zqi_qYC4ZdhUQ@mail.gmail.com>
On 5/16/25 10:31 AM, Caleb Sander Mateos wrote:
>> @@ -1442,10 +1462,11 @@ void __io_submit_flush_completions(struct io_ring_ctx *ctx)
>> unlikely(!io_fill_cqe_req(ctx, req))) {
>> if (ctx->lockless_cq) {
>> spin_lock(&ctx->completion_lock);
>> - io_req_cqe_overflow(req);
>> + io_req_cqe_overflow(req, GFP_ATOMIC);
>> spin_unlock(&ctx->completion_lock);
>> } else {
>> - io_req_cqe_overflow(req);
>> + gfp_t gfp = ctx->lockless_cq ? GFP_KERNEL : GFP_ATOMIC;
>
> This is in the else case of an if (ctx->lockless_cq). Isn't
> ctx->lockless_cq known to be false?
Indeed! Actually this part needs to be split too. I'll redo this one.
--
Jens Axboe
next prev parent reply other threads:[~2025-05-16 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 16:08 [PATCHSET 0/2] Allow non-atomic allocs for overflows Jens Axboe
2025-05-16 16:08 ` [PATCH 1/2] io_uring: split alloc and add of overflow Jens Axboe
2025-05-16 16:31 ` Caleb Sander Mateos
2025-05-16 16:33 ` Jens Axboe [this message]
2025-05-16 16:43 ` Pavel Begunkov
2025-05-16 16:44 ` Jens Axboe
2025-05-16 16:58 ` Pavel Begunkov
2025-05-16 16:57 ` Jens Axboe
2025-05-16 18:27 ` Pavel Begunkov
2025-05-16 16:08 ` [PATCH 2/2] io_uring: make io_alloc_ocqe() take a struct io_cqe pointer 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=9bf4b0e9-df89-4f8d-8562-7122e57a47b0@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=csander@purestorage.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