From: David Wei <[email protected]>
To: Jens Axboe <[email protected]>, io-uring <[email protected]>
Subject: Re: [PATCH] io_uring/napi: enable even with a timeout of 0
Date: Thu, 15 Feb 2024 15:37:14 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2024-02-15 15:32, Jens Axboe wrote:
> 1 usec is not as short as it used to be, and it makes sense to allow 0
> for a busy poll timeout - this means just do one loop to check if we
> have anything available. Add a separate ->napi_enabled to check if napi
> has been enabled or not.
>
> While at it, move the writing of the ctx napi values after we've copied
> the old values back to userspace. This ensures that if the call fails,
> we'll be in the same state as we were before, rather than some
> indeterminate state.
>
> Signed-off-by: Jens Axboe <[email protected]>
>
> ---
>
> diff --git a/include/linux/io_uring_types.h b/include/linux/io_uring_types.h
> index 4fe7af8a4907..bd7071aeec5d 100644
> --- a/include/linux/io_uring_types.h
> +++ b/include/linux/io_uring_types.h
> @@ -420,6 +420,7 @@ struct io_ring_ctx {
> /* napi busy poll default timeout */
> unsigned int napi_busy_poll_to;
> bool napi_prefer_busy_poll;
> + bool napi_enabled;
>
> DECLARE_HASHTABLE(napi_ht, 4);
> #endif
> diff --git a/io_uring/napi.c b/io_uring/napi.c
> index b234adda7dfd..e653927a376e 100644
> --- a/io_uring/napi.c
> +++ b/io_uring/napi.c
> @@ -227,12 +227,12 @@ int io_register_napi(struct io_ring_ctx *ctx, void __user *arg)
> if (napi.pad[0] || napi.pad[1] || napi.pad[2] || napi.resv)
> return -EINVAL;
>
> - WRITE_ONCE(ctx->napi_busy_poll_to, napi.busy_poll_to);
> - WRITE_ONCE(ctx->napi_prefer_busy_poll, !!napi.prefer_busy_poll);
> -
> if (copy_to_user(arg, &curr, sizeof(curr)))
> return -EFAULT;
>
> + WRITE_ONCE(ctx->napi_busy_poll_to, napi.busy_poll_to);
> + WRITE_ONCE(ctx->napi_prefer_busy_poll, !!napi.prefer_busy_poll);
> + WRITE_ONCE(ctx->napi_enabled, true);
> return 0;
> }
>
> @@ -256,6 +256,7 @@ int io_unregister_napi(struct io_ring_ctx *ctx, void __user *arg)
>
> WRITE_ONCE(ctx->napi_busy_poll_to, 0);
> WRITE_ONCE(ctx->napi_prefer_busy_poll, false);
> + WRITE_ONCE(ctx->napi_enabled, true);
Should this be false?
> return 0;
> }
>
> @@ -300,7 +301,7 @@ void __io_napi_busy_loop(struct io_ring_ctx *ctx, struct io_wait_queue *iowq)
> {
> iowq->napi_prefer_busy_poll = READ_ONCE(ctx->napi_prefer_busy_poll);
>
> - if (!(ctx->flags & IORING_SETUP_SQPOLL) && iowq->napi_busy_poll_to)
> + if (!(ctx->flags & IORING_SETUP_SQPOLL) && ctx->napi_enabled)
> io_napi_blocking_busy_loop(ctx, iowq);
> }
>
next prev parent reply other threads:[~2024-02-15 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 22:32 [PATCH] io_uring/napi: enable even with a timeout of 0 Jens Axboe
2024-02-15 22:37 ` David Wei [this message]
2024-02-15 22:37 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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