From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH 05/11] eventpoll: add ep_poll_queue() loop
Date: Fri, 7 Feb 2025 12:28:17 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/4/25 19:46, Jens Axboe wrote:
> If a wait_queue_entry is passed in to epoll_wait(), then utilize this
> new helper for reaping events and/or adding to the epoll waitqueue
> rather than calling the potentially sleeping ep_poll(). It works like
> ep_poll(), except it doesn't block - it either returns the events that
> are already available, or it adds the specified entry to the struct
> eventpoll waitqueue to get a callback when events are triggered. It
> returns -EIOCBQUEUED for that case.
>
> Signed-off-by: Jens Axboe <[email protected]>
> ---
> fs/eventpoll.c | 37 ++++++++++++++++++++++++++++++++++++-
> 1 file changed, 36 insertions(+), 1 deletion(-)
>
> diff --git a/fs/eventpoll.c b/fs/eventpoll.c
> index ecaa5591f4be..a8be0c7110e4 100644
> --- a/fs/eventpoll.c
> +++ b/fs/eventpoll.c
> @@ -2032,6 +2032,39 @@ static int ep_try_send_events(struct eventpoll *ep,
> return res;
> }
>
> +static int ep_poll_queue(struct eventpoll *ep,
> + struct epoll_event __user *events, int maxevents,
> + struct wait_queue_entry *wait)
> +{
> + int res, eavail;
> +
> + /* See ep_poll() for commentary */
> + eavail = ep_events_available(ep);
> + while (1) {
> + if (eavail) {
> + res = ep_try_send_events(ep, events, maxevents);
> + if (res)
> + return res;
> + }
> +
> + eavail = ep_busy_loop(ep, true);
I have doubts we want to busy loop here even if it's just one iteration /
nonblockinf. And there is already napi polling support in io_uring done
from the right for io_uring users spot.
--
Pavel Begunkov
next prev parent reply other threads:[~2025-02-07 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 19:46 [PATCHSET v2 0/11] io_uring epoll wait support Jens Axboe
2025-02-04 19:46 ` [PATCH 01/11] eventpoll: abstract out main epoll reaper into a function Jens Axboe
2025-02-04 19:46 ` [PATCH 02/11] eventpoll: add helper to remove wait entry from wait queue head Jens Axboe
2025-02-04 19:46 ` [PATCH 03/11] eventpoll: abstract out ep_try_send_events() helper Jens Axboe
2025-02-04 19:46 ` [PATCH 04/11] eventpoll: add struct wait_queue_entry argument to epoll_wait() Jens Axboe
2025-02-04 19:46 ` [PATCH 05/11] eventpoll: add ep_poll_queue() loop Jens Axboe
2025-02-07 12:28 ` Pavel Begunkov [this message]
2025-02-07 14:29 ` Jens Axboe
2025-02-04 19:46 ` [PATCH 06/11] io_uring/epoll: remove CONFIG_EPOLL guards Jens Axboe
2025-02-04 19:46 ` [PATCH 07/11] io_uring/poll: pull ownership handling into poll.h Jens Axboe
2025-02-04 19:46 ` [PATCH 08/11] io_uring/poll: add IO_POLL_FINISH_FLAG Jens Axboe
2025-02-07 12:15 ` Pavel Begunkov
2025-02-07 14:29 ` Jens Axboe
2025-02-04 19:46 ` [PATCH 09/11] io_uring/epoll: add support for IORING_OP_EPOLL_WAIT Jens Axboe
2025-02-07 12:38 ` Pavel Begunkov
2025-02-07 17:13 ` Jens Axboe
2025-02-04 19:46 ` [PATCH 10/11] io_uring/epoll: add support for provided buffers Jens Axboe
2025-02-04 19:46 ` [PATCH 11/11] io_uring/epoll: add multishot support for IORING_OP_EPOLL_WAIT 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] \
[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