public inbox for [email protected]
 help / color / mirror / Atom feed
* [PATCH] io_uring/uring_cmd: take advantage of completion batching
@ 2023-04-12 18:09 Jens Axboe
  2023-04-13  2:02 ` Ming Lei
  0 siblings, 1 reply; 2+ messages in thread
From: Jens Axboe @ 2023-04-12 18:09 UTC (permalink / raw)
  To: io-uring

We know now what the completion context is for the uring_cmd completion
handling, so use that to have io_req_task_complete() decide what the
best way to complete the request is. This allows batching of the posted
completions if we have multiple pending, rather than always doing them
one-by-one.

Signed-off-by: Jens Axboe <[email protected]>

---

diff --git a/io_uring/uring_cmd.c b/io_uring/uring_cmd.c
index f7a96bc76ea1..5113c9a48583 100644
--- a/io_uring/uring_cmd.c
+++ b/io_uring/uring_cmd.c
@@ -54,11 +54,15 @@ void io_uring_cmd_done(struct io_uring_cmd *ioucmd, ssize_t ret, ssize_t res2,
 	io_req_set_res(req, ret, 0);
 	if (req->ctx->flags & IORING_SETUP_CQE32)
 		io_req_set_cqe32_extra(req, res2, 0);
-	if (req->ctx->flags & IORING_SETUP_IOPOLL)
+	if (req->ctx->flags & IORING_SETUP_IOPOLL) {
 		/* order with io_iopoll_req_issued() checking ->iopoll_complete */
 		smp_store_release(&req->iopoll_completed, 1);
-	else
-		io_req_complete_post(req, issue_flags);
+	} else {
+		struct io_tw_state ts = {
+			.locked = !(issue_flags & IO_URING_F_UNLOCKED),
+		};
+		io_req_task_complete(req, &ts);
+	}
 }
 EXPORT_SYMBOL_GPL(io_uring_cmd_done);
 
-- 
Jens Axboe


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] io_uring/uring_cmd: take advantage of completion batching
  2023-04-12 18:09 [PATCH] io_uring/uring_cmd: take advantage of completion batching Jens Axboe
@ 2023-04-13  2:02 ` Ming Lei
  0 siblings, 0 replies; 2+ messages in thread
From: Ming Lei @ 2023-04-13  2:02 UTC (permalink / raw)
  To: Jens Axboe; +Cc: io-uring, ming.lei

On Wed, Apr 12, 2023 at 12:09:18PM -0600, Jens Axboe wrote:
> We know now what the completion context is for the uring_cmd completion
> handling, so use that to have io_req_task_complete() decide what the
> best way to complete the request is. This allows batching of the posted
> completions if we have multiple pending, rather than always doing them
> one-by-one.
> 
> Signed-off-by: Jens Axboe <[email protected]>
> 
> ---
> 
> diff --git a/io_uring/uring_cmd.c b/io_uring/uring_cmd.c
> index f7a96bc76ea1..5113c9a48583 100644
> --- a/io_uring/uring_cmd.c
> +++ b/io_uring/uring_cmd.c
> @@ -54,11 +54,15 @@ void io_uring_cmd_done(struct io_uring_cmd *ioucmd, ssize_t ret, ssize_t res2,
>  	io_req_set_res(req, ret, 0);
>  	if (req->ctx->flags & IORING_SETUP_CQE32)
>  		io_req_set_cqe32_extra(req, res2, 0);
> -	if (req->ctx->flags & IORING_SETUP_IOPOLL)
> +	if (req->ctx->flags & IORING_SETUP_IOPOLL) {
>  		/* order with io_iopoll_req_issued() checking ->iopoll_complete */
>  		smp_store_release(&req->iopoll_completed, 1);
> -	else
> -		io_req_complete_post(req, issue_flags);
> +	} else {
> +		struct io_tw_state ts = {
> +			.locked = !(issue_flags & IO_URING_F_UNLOCKED),
> +		};
> +		io_req_task_complete(req, &ts);
> +	}

Looks fine,

Reviewed-by: Ming Lei <[email protected]>

BTW, looks a little IOPS improvement is observed when running t/io_uring
on ublk/null with two queues, but not very obvious.

Thanks,
Ming


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-04-13  2:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-04-12 18:09 [PATCH] io_uring/uring_cmd: take advantage of completion batching Jens Axboe
2023-04-13  2:02 ` Ming Lei

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox