public inbox for [email protected]
 help / color / mirror / Atom feed
From: Hao Xu <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH 9/9] io_uring: allow events update of running poll requests
Date: Fri, 19 Mar 2021 11:31:26 +0800	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

在 2021/3/18 上午12:29, Jens Axboe 写道:
> This adds a new POLL_ADD flag, IORING_POLL_UPDATE. As with the other
> POLL_ADD flag, this one is masked into sqe->len. If set, the POLL_ADD
> will have the following behavior:
> 
> - sqe->addr must contain the the user_data of the poll request that
>    needs to be modified. This field is otherwise invalid for a POLL_ADD
>    command.
> 
> - sqe->poll_events must contain the new mask for the existing poll
>    request. There are no checks for whether these are identical or not,
>    if a matching poll request is found, then it is re-armed with the new
>    mask.
> 
> A POLL_ADD with the IORING_POLL_UPDATE flag set may complete with any
> of the following results:
> 
> 1) 0, which means that we successfully found the existing poll request
>     specified, and performed the re-arm procedure. Any error from that
>     re-arm will be exposed as a completion event for that original poll
>     request, not for the update request.
> 2) -ENOENT, if no existing poll request was found with the given
>     user_data.
> 3) -EALREADY, if the existing poll request was already in the process of
>     being removed/canceled/completing.
> 4) -EACCES, if an attempt was made to modify an internal poll request
>     (eg not one originally issued ass IORING_OP_POLL_ADD).
> 
> The usual -EINVAL cases apply as well, if any invalid fields are set
> in the sqe for this command type.
> 
> Signed-off-by: Jens Axboe <[email protected]>
> ---
>   fs/io_uring.c                 | 73 ++++++++++++++++++++++++++++++++---
>   include/uapi/linux/io_uring.h |  4 ++
>   2 files changed, 72 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 8ed363bd95aa..79a40364e041 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -467,10 +467,14 @@ struct io_ring_ctx {
>    */
>   struct io_poll_iocb {
>   	struct file			*file;
> -	struct wait_queue_head		*head;
> +	union {
> +		struct wait_queue_head	*head;
> +		u64			addr;
> +	};
>   	__poll_t			events;
>   	bool				done;
>   	bool				canceled;
> +	bool				update;
>   	struct wait_queue_entry		wait;
>   };
>   
> @@ -5004,6 +5008,7 @@ static void io_init_poll_iocb(struct io_poll_iocb *poll, __poll_t events,
>   	poll->head = NULL;
>   	poll->done = false;
>   	poll->canceled = false;
> +	poll->update = false;
>   	poll->events = events;
>   	INIT_LIST_HEAD(&poll->wait.entry);
>   	init_waitqueue_func_entry(&poll->wait, wake_func);
> @@ -5382,24 +5387,32 @@ static int io_poll_add_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe
>   
>   	if (unlikely(req->ctx->flags & IORING_SETUP_IOPOLL))
>   		return -EINVAL;
> -	if (sqe->addr || sqe->ioprio || sqe->off || sqe->buf_index)
> +	if (sqe->ioprio || sqe->off || sqe->buf_index)
>   		return -EINVAL;
>   	flags = READ_ONCE(sqe->len);
> -	if (flags & ~IORING_POLL_ADD_MULTI)
> +	if (flags & ~(IORING_POLL_ADD_MULTI | IORING_POLL_UPDATE))
>   		return -EINVAL;
>   
>   	events = READ_ONCE(sqe->poll32_events);
>   #ifdef __BIG_ENDIAN
>   	events = swahw32(events);
>   #endif
> -	if (!flags)
> +	if (!(flags & IORING_POLL_ADD_MULTI))
>   		events |= EPOLLONESHOT;
> +	if (flags & IORING_POLL_UPDATE) {
> +		poll->update = true;
> +		poll->addr = READ_ONCE(sqe->addr);
> +	} else {
> +		if (sqe->addr)
> +			return -EINVAL;
> +		poll->update = false;
Hi Jens, is `poll->update = false` redundant?
> +	}
>   	poll->events = demangle_poll(events) | EPOLLERR | EPOLLHUP |
>   		       (events & (EPOLLEXCLUSIVE|EPOLLONESHOT));
>   	return 0;
>   }
>   
> -static int io_poll_add(struct io_kiocb *req, unsigned int issue_flags)
> +static int __io_poll_add(struct io_kiocb *req)
>   {
>   	struct io_poll_iocb *poll = &req->poll;
>   	struct io_ring_ctx *ctx = req->ctx;
> @@ -5425,6 +5438,56 @@ static int io_poll_add(struct io_kiocb *req, unsigned int issue_flags)
>   	return ipt.error;
>   }
>   
> +static int io_poll_update(struct io_kiocb *req)
> +{
> +	struct io_ring_ctx *ctx = req->ctx;
> +	struct io_kiocb *preq;
> +	int ret;
> +
> +	spin_lock_irq(&ctx->completion_lock);
> +	preq = io_poll_find(ctx, req->poll.addr);
> +	if (!preq) {
> +		ret = -ENOENT;
> +		goto err;
> +	} else if (preq->opcode != IORING_OP_POLL_ADD) {
> +		/* don't allow internal poll updates */
> +		ret = -EACCES;
> +		goto err;
> +	}
> +	if (!__io_poll_remove_one(preq, &preq->poll)) {
> +		/* in process of completing/removal */
> +		ret = -EALREADY;
> +		goto err;
> +	}
> +	/* we now have a detached poll request. reissue. */
> +	ret = 0;
> +err:
> +	spin_unlock_irq(&ctx->completion_lock);
> +	if (ret < 0) {
> +		req_set_fail_links(req);
> +finish:
> +		io_req_complete(req, ret);
> +		return 0;
> +	}
> +	/* only mask one event flags, keep behavior flags */
> +	preq->poll.events &= ~0xffff;
> +	preq->poll.events |= req->poll.events & 0xffff;
> +	ret = __io_poll_add(preq);
> +	if (ret < 0) {
> +		req_set_fail_links(preq);
> +		io_req_complete(preq, ret);
> +	}
> +	ret = 0;
> +	goto finish;
> +}
> +
> +static int io_poll_add(struct io_kiocb *req, unsigned int issue_flags)
> +{
> +	if (!req->poll.update)
> +		return __io_poll_add(req);
> +	return io_poll_update(req);
> +}
> +
>   static enum hrtimer_restart io_timeout_fn(struct hrtimer *timer)
>   {
>   	struct io_timeout_data *data = container_of(timer,
> diff --git a/include/uapi/linux/io_uring.h b/include/uapi/linux/io_uring.h
> index 76c967621601..44fe7f80c851 100644
> --- a/include/uapi/linux/io_uring.h
> +++ b/include/uapi/linux/io_uring.h
> @@ -166,8 +166,12 @@ enum {
>    * IORING_POLL_ADD_MULTI	Multishot poll. Sets IORING_CQE_F_MORE if
>    *				the poll handler will continue to report
>    *				CQEs on behalf of the same SQE.
> + *
> + * IORING_POLL_UPDATE		Update existing poll request, matching
> + *				sqe->addr as the old user_data field.
>    */
>   #define IORING_POLL_ADD_MULTI	(1U << 0)
> +#define IORING_POLL_UPDATE	(1U << 1)
>   
>   /*
>    * IO completion data structure (Completion Queue Entry)
> 


  reply	other threads:[~2021-03-19  3:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 16:29 [PATCHSET for-next 0/9] Poll improvements Jens Axboe
2021-03-17 16:29 ` [PATCH 1/9] io_uring: correct comment on poll vs iopoll Jens Axboe
2021-03-17 16:29 ` [PATCH 2/9] io_uring: transform ret == 0 for poll cancelation completions Jens Axboe
2021-03-17 16:29 ` [PATCH 3/9] io_uring: allocate memory for overflowed CQEs Jens Axboe
2021-03-17 16:29 ` [PATCH 4/9] io_uring: include cflags in completion trace event Jens Axboe
2021-03-17 16:29 ` [PATCH 5/9] io_uring: add multishot mode for IORING_OP_POLL_ADD Jens Axboe
2021-03-17 16:29 ` [PATCH 6/9] io_uring: abstract out helper for removing poll waitqs/hashes Jens Axboe
2021-03-17 16:29 ` [PATCH 7/9] io_uring: terminate multishot poll for CQ ring overflow Jens Axboe
2021-03-17 16:29 ` [PATCH 8/9] io_uring: abstract out a io_poll_find_helper() Jens Axboe
2021-03-17 16:29 ` [PATCH 9/9] io_uring: allow events update of running poll requests Jens Axboe
2021-03-19  3:31   ` Hao Xu [this message]
2021-03-19 13: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 \
    --in-reply-to=5c62f6bf-057c-e4b1-5cbf-102e73f8bfcc@linux.alibaba.com \
    [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