From: Caleb Sander Mateos <csander@purestorage.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, asml.silence@gmail.com
Subject: Re: [PATCH 5/5] io_uring: add new helpers for posting overflows
Date: Fri, 16 May 2025 16:17:05 -0700 [thread overview]
Message-ID: <CADUfDZq19zOMkX2ZnaAuftb=jCGXRfje+UNu9xmR3gnGBSACMA@mail.gmail.com> (raw)
In-Reply-To: <20250516201007.482667-6-axboe@kernel.dk>
On Fri, May 16, 2025 at 1:10 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> Add two helpers, one for posting overflows for lockless_cq rings, and
> one for non-lockless_cq rings. The former can allocate sanely with
> GFP_KERNEL, but needs to grab the completion lock for posting, while the
> latter must do non-sleeping allocs as it already holds the completion
> lock.
>
> While at it, mark the overflow handling functions as __cold as well, as
> they should not generally be called during normal operations of the
> ring.
>
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> ---
> io_uring/io_uring.c | 50 ++++++++++++++++++++++++++-------------------
> 1 file changed, 29 insertions(+), 21 deletions(-)
>
> diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
> index c66fc4b7356b..52087b079a0c 100644
> --- a/io_uring/io_uring.c
> +++ b/io_uring/io_uring.c
> @@ -697,8 +697,8 @@ static __cold void io_uring_drop_tctx_refs(struct task_struct *task)
> }
> }
>
> -static bool io_cqring_add_overflow(struct io_ring_ctx *ctx,
> - struct io_overflow_cqe *ocqe)
> +static __cold bool io_cqring_add_overflow(struct io_ring_ctx *ctx,
> + struct io_overflow_cqe *ocqe)
> {
> lockdep_assert_held(&ctx->completion_lock);
>
> @@ -808,6 +808,27 @@ static bool io_fill_cqe_aux(struct io_ring_ctx *ctx, u64 user_data, s32 res,
> return false;
> }
>
> +static __cold void io_cqe_overflow_lockless(struct io_ring_ctx *ctx,
> + struct io_cqe *cqe,
> + struct io_big_cqe *big_cqe)
Naming nit: "lockless" seems a bit misleading since this does still
take the completion_lock. Maybe name this function "io_cqe_overflow()"
and the other "io_cqe_overflow_locked()"?
Otherwise,
Reviewed-by: Caleb Sander Mateos <csander@purestorage.com>
> +{
> + struct io_overflow_cqe *ocqe;
> +
> + ocqe = io_alloc_ocqe(ctx, cqe, big_cqe, GFP_KERNEL);
> + spin_lock(&ctx->completion_lock);
> + io_cqring_add_overflow(ctx, ocqe);
> + spin_unlock(&ctx->completion_lock);
> +}
> +
> +static __cold bool io_cqe_overflow(struct io_ring_ctx *ctx, struct io_cqe *cqe,
> + struct io_big_cqe *big_cqe)
> +{
> + struct io_overflow_cqe *ocqe;
> +
> + ocqe = io_alloc_ocqe(ctx, cqe, big_cqe, GFP_ATOMIC);
> + return io_cqring_add_overflow(ctx, ocqe);
> +}
> +
> #define io_init_cqe(user_data, res, cflags) \
> (struct io_cqe) { .user_data = user_data, .res = res, .flags = cflags }
>
> @@ -818,11 +839,9 @@ bool io_post_aux_cqe(struct io_ring_ctx *ctx, u64 user_data, s32 res, u32 cflags
> io_cq_lock(ctx);
> filled = io_fill_cqe_aux(ctx, user_data, res, cflags);
> if (unlikely(!filled)) {
> - struct io_overflow_cqe *ocqe;
> struct io_cqe cqe = io_init_cqe(user_data, res, cflags);
>
> - ocqe = io_alloc_ocqe(ctx, &cqe, NULL, GFP_ATOMIC);
> - filled = io_cqring_add_overflow(ctx, ocqe);
> + filled = io_cqe_overflow(ctx, &cqe, NULL);
> }
> io_cq_unlock_post(ctx);
> return filled;
> @@ -838,13 +857,9 @@ void io_add_aux_cqe(struct io_ring_ctx *ctx, u64 user_data, s32 res, u32 cflags)
> lockdep_assert(ctx->lockless_cq);
>
> if (!io_fill_cqe_aux(ctx, user_data, res, cflags)) {
> - struct io_overflow_cqe *ocqe;
> struct io_cqe cqe = io_init_cqe(user_data, res, cflags);
>
> - ocqe = io_alloc_ocqe(ctx, &cqe, NULL, GFP_KERNEL);
> - spin_lock(&ctx->completion_lock);
> - io_cqring_add_overflow(ctx, ocqe);
> - spin_unlock(&ctx->completion_lock);
> + io_cqe_overflow_lockless(ctx, &cqe, NULL);
> }
> ctx->submit_state.cq_flush = true;
> }
> @@ -1448,17 +1463,10 @@ 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, &req->big_cqe, gfp);
> - if (ctx->lockless_cq) {
> - spin_lock(&ctx->completion_lock);
> - io_cqring_add_overflow(ctx, ocqe);
> - spin_unlock(&ctx->completion_lock);
> - } else {
> - io_cqring_add_overflow(ctx, ocqe);
> - }
> + if (ctx->lockless_cq)
> + io_cqe_overflow_lockless(ctx, &req->cqe, &req->big_cqe);
> + else
> + io_cqe_overflow(ctx, &req->cqe, &req->big_cqe);
> }
> }
> __io_cq_unlock_post(ctx);
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-05-16 23:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 20:05 [PATCHSET v3 0/5] Allow non-atomic allocs for overflows Jens Axboe
2025-05-16 20:05 ` [PATCH 1/5] io_uring: open code io_req_cqe_overflow() 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
2025-05-16 20:05 ` [PATCH 3/5] io_uring: make io_alloc_ocqe() take a struct io_cqe pointer Jens Axboe
2025-05-16 23:07 ` Caleb Sander Mateos
2025-05-16 23:08 ` Caleb Sander Mateos
2025-05-16 23:48 ` Jens Axboe
2025-05-16 20:05 ` [PATCH 4/5] io_uring: pass in struct io_big_cqe to io_alloc_ocqe() Jens Axboe
2025-05-16 23:10 ` Caleb Sander Mateos
2025-05-16 20:05 ` [PATCH 5/5] io_uring: add new helpers for posting overflows Jens Axboe
2025-05-16 23:17 ` Caleb Sander Mateos [this message]
2025-05-16 23:49 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-05-17 11:42 [PATCHSET v4 0/5] Allow non-atomic allocs for overflows 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
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='CADUfDZq19zOMkX2ZnaAuftb=jCGXRfje+UNu9xmR3gnGBSACMA@mail.gmail.com' \
--to=csander@purestorage.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--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