public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Olivier Langlois <[email protected]>,
	Jens Axboe <[email protected]>,
	[email protected]
Subject: Re: [PATCH] io_uring: keep multishot request NAPI timeout fresh
Date: Tue, 30 Jul 2024 12:08:39 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <0fe61a019ec61e5708cd117cb42ed0dab95e1617.1722294646.git.olivier@trillion01.com>

On 7/30/24 00:03, Olivier Langlois wrote:
> this refresh statement was originally present in the original patch:
> https://lore.kernel.org/netdev/[email protected]/
> 
> it has been removed with no explanation in v6:
> https://lore.kernel.org/netdev/[email protected]/
> 
> it is important to make the refresh for multishot request because if no
> new requests using the same NAPI device are added to the ring, the entry
> will become stall and be removed silently and the unsuspecting user will
> not know that his ring made busy polling for only 60 seconds.

we probably need a new update helper in the future, but good
enough for now.

Reviewed-by: Pavel Begunkov <[email protected]>

Should also have:

Fixes: 8d0c12a80cdeb ("io-uring: add napi busy poll support")
Cc: [email protected]


> Signed-off-by: Olivier Langlois <[email protected]>
> ---
>   io_uring/poll.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/io_uring/poll.c b/io_uring/poll.c
> index 0a8e02944689..1f63b60e85e7 100644
> --- a/io_uring/poll.c
> +++ b/io_uring/poll.c
> @@ -347,6 +347,7 @@ static int io_poll_check_events(struct io_kiocb *req, struct io_tw_state *ts)
>   		v &= IO_POLL_REF_MASK;
>   	} while (atomic_sub_return(v, &req->poll_refs) & IO_POLL_REF_MASK);
>   
> +	io_napi_add(req);
>   	return IOU_POLL_NO_ACTION;
>   }
>   

-- 
Pavel Begunkov

  reply	other threads:[~2024-07-30 11:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 23:03 [PATCH] io_uring: keep multishot request NAPI timeout fresh Olivier Langlois
2024-07-30 11:08 ` Pavel Begunkov [this message]
2024-07-30 12:20 ` 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] \
    [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