public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
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 2/5] io_uring: split alloc and add of overflow
Date: Sat, 17 May 2025 18:48:44 -0600	[thread overview]
Message-ID: <94b773a8-6232-419c-821e-9fc18e545a60@kernel.dk> (raw)
In-Reply-To: <CADUfDZqC5M8vH0PJ9Pqc-oesznP=OX0BN2sK9DdosHGhmV-VYg@mail.gmail.com>

On 5/17/25 5:30 PM, Caleb Sander Mateos wrote:
>> @@ -1425,20 +1441,19 @@ void __io_submit_flush_completions(struct io_ring_ctx *ctx)
>>                  */
>>                 if (!(req->flags & (REQ_F_CQE_SKIP | REQ_F_REISSUE)) &&
>>                     unlikely(!io_fill_cqe_req(ctx, req))) {
>> +                       gfp_t gfp = ctx->lockless_cq ? GFP_KERNEL : GFP_ATOMIC;
>> +                       struct io_overflow_cqe *ocqe;
>> +
>> +                       ocqe = io_alloc_ocqe(ctx, req->cqe.user_data, req->cqe.res,
>> +                                            req->cqe.flags, req->big_cqe.extra1,
>> +                                            req->big_cqe.extra2, gfp);
>>                         if (ctx->lockless_cq) {
>>                                 spin_lock(&ctx->completion_lock);
>> -                               io_cqring_event_overflow(req->ctx, req->cqe.user_data,
>> -                                                       req->cqe.res, req->cqe.flags,
>> -                                                       req->big_cqe.extra1,
>> -                                                       req->big_cqe.extra2);
>> +                               io_cqring_add_overflow(ctx, ocqe);
>>                                 spin_unlock(&ctx->completion_lock);
>>                         } else {
>> -                               io_cqring_event_overflow(req->ctx, req->cqe.user_data,
>> -                                                       req->cqe.res, req->cqe.flags,
>> -                                                       req->big_cqe.extra1,
>> -                                                       req->big_cqe.extra2);
>> +                               io_cqring_add_overflow(ctx, ocqe);
>>                         }
>> -
>>                         memset(&req->big_cqe, 0, sizeof(req->big_cqe));
> 
> Stray whitespace change. Either drop it or move it to the previous
> patch which added the blank line?

Thanks, I'll drop it here, patch 4/5 kills it anyway with removing the
memset.

-- 
Jens Axboe

  reply	other threads:[~2025-05-18  0:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17 11:42 [PATCHSET v4 0/5] Allow non-atomic allocs for overflows Jens Axboe
2025-05-17 11:42 ` [PATCH 1/5] io_uring: open code io_req_cqe_overflow() Jens Axboe
2025-05-17 11:42 ` [PATCH 2/5] io_uring: split alloc and add of overflow Jens Axboe
2025-05-17 23:30   ` Caleb Sander Mateos
2025-05-18  0:48     ` Jens Axboe [this message]
2025-05-17 11:42 ` [PATCH 3/5] io_uring: make io_alloc_ocqe() take a struct io_cqe pointer Jens Axboe
2025-05-17 23:28   ` Caleb Sander Mateos
2025-05-17 11:42 ` [PATCH 4/5] io_uring: pass in struct io_big_cqe to io_alloc_ocqe() Jens Axboe
2025-05-17 11:42 ` [PATCH 5/5] io_uring: add new helpers for posting overflows Jens Axboe
2025-05-17 23:32   ` Caleb Sander Mateos
  -- strict thread matches above, loose matches on Subject: below --
2025-05-16 20:05 [PATCHSET v3 0/5] Allow non-atomic allocs for overflows Jens Axboe
2025-05-16 20:05 ` [PATCH 2/5] io_uring: split alloc and add of overflow Jens Axboe
2025-05-16 23:00   ` Caleb Sander Mateos

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=94b773a8-6232-419c-821e-9fc18e545a60@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