public inbox for [email protected]
 help / color / mirror / Atom feed
From: Hao Xu <[email protected]>
To: Dylan Yudaken <[email protected]>, Jens Axboe <[email protected]>,
	Pavel Begunkov <[email protected]>,
	[email protected]
Cc: [email protected]
Subject: Re: [PATCH for-next v3 0/7] io_uring: defer task work to when it is needed
Date: Mon, 29 Aug 2022 15:01:16 +0800	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 8/19/22 20:19, Dylan Yudaken wrote:
> We have seen workloads which suffer due to the way task work is currently
> scheduled. This scheduling can cause non-trivial tasks to run interrupting
> useful work on the workload. For example in network servers, a large async
> recv may run, calling memcpy on a large packet, interrupting a send. Which
> would add latency.
> 
> This series adds an option to defer async work until user space calls
> io_uring_enter with the GETEVENTS flag. This allows the workload to choose
> when to schedule async work and have finer control (at the expense of
> complexity of managing this) of scheduling.
> 
> Patches 1,2 are prep patches
> Patch 3 changes io_uring_enter to not pre-run task work
> Patch 4/5/6 adds the new flag and functionality
> Patch 7 adds tracing for the local task work running
> 
> Changes since v2:
>   - add a patch to trace local task work run
>   - return -EEXIST if calling from the wrong task
>   - properly handle shutting down due to an exec
>   - remove 'all' parameter from io_run_task_work_ctx
>   
> Changes since v1:
>   - Removed the first patch (using ctx variable) which was broken
>   - Require IORING_SETUP_SINGLE_ISSUER and make sure waiter task
>     is the same as the submitter task
>   - Just don't run task work at the start of io_uring_enter (Pavel's
>     suggestion)
>   - Remove io_move_task_work_from_local
>   - Fix locking bugs
> 
> Dylan Yudaken (7):
>    io_uring: remove unnecessary variable
>    io_uring: introduce io_has_work
>    io_uring: do not run task work at the start of io_uring_enter
>    io_uring: add IORING_SETUP_DEFER_TASKRUN
>    io_uring: move io_eventfd_put
>    io_uring: signal registered eventfd to process deferred task work
>    io_uring: trace local task work run
> 
>   include/linux/io_uring_types.h  |   3 +
>   include/trace/events/io_uring.h |  29 ++++
>   include/uapi/linux/io_uring.h   |   7 +
>   io_uring/cancel.c               |   2 +-
>   io_uring/io_uring.c             | 264 ++++++++++++++++++++++++++------
>   io_uring/io_uring.h             |  29 +++-
>   io_uring/rsrc.c                 |   2 +-
>   7 files changed, 285 insertions(+), 51 deletions(-)
> 
> 
> base-commit: 5993000dc6b31b927403cee65fbc5f9f070fa3e4
> prerequisite-patch-id: cb1d024945aa728d09a131156140a33d30bc268b

Apart from the comments, others looks good to me,

Acked-by: Hao Xu <[email protected]>


      parent reply	other threads:[~2022-08-29  7:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 12:19 [PATCH for-next v3 0/7] io_uring: defer task work to when it is needed Dylan Yudaken
2022-08-19 12:19 ` [PATCH for-next v3 1/7] io_uring: remove unnecessary variable Dylan Yudaken
2022-08-19 12:19 ` [PATCH for-next v3 2/7] io_uring: introduce io_has_work Dylan Yudaken
2022-08-19 12:19 ` [PATCH for-next v3 3/7] io_uring: do not run task work at the start of io_uring_enter Dylan Yudaken
2022-08-19 12:19 ` [PATCH for-next v3 4/7] io_uring: add IORING_SETUP_DEFER_TASKRUN Dylan Yudaken
2022-08-22 11:34   ` Pavel Begunkov
2022-08-29  6:32     ` Hao Xu
2022-08-30  7:23       ` Dylan Yudaken
2022-08-30  7:54         ` Hao Xu
2022-08-30  9:54     ` Dylan Yudaken
2022-08-30 10:29       ` Pavel Begunkov
2022-08-30 13:19   ` Hao Xu
2022-08-30 13:34     ` Dylan Yudaken
2022-08-30 14:04       ` Hao Xu
2022-08-19 12:19 ` [PATCH for-next v3 5/7] io_uring: move io_eventfd_put Dylan Yudaken
2022-08-19 12:19 ` [PATCH for-next v3 6/7] io_uring: signal registered eventfd to process deferred task work Dylan Yudaken
2022-08-19 12:19 ` [PATCH for-next v3 7/7] io_uring: trace local task work run Dylan Yudaken
2022-08-29  7:01 ` Hao Xu [this message]

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] \
    [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