public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Dylan Yudaken <[email protected]>,
	[email protected], Pavel Begunkov <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH for-next v4 0/7] io_uring: defer task work to when it is needed
Date: Tue, 30 Aug 2022 08:30:22 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Tue, 30 Aug 2022 05:50:06 -0700, 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.
> 
> [...]

Applied, thanks!

[1/7] io_uring: remove unnecessary variable
      commit: e2f73811084cb6f4821cbe6e53bb0d9407af52f5
[2/7] io_uring: introduce io_has_work
      commit: cb0101159452eb63d0facf806e0a868963a11035
[3/7] io_uring: do not run task work at the start of io_uring_enter
      commit: 415f872f5f3aedb62bf857c6e315a88e26c08aaa
[4/7] io_uring: add IORING_SETUP_DEFER_TASKRUN
      commit: 2a23c7a52405c17183f36ef4aefb1fcf44425c2d
[5/7] io_uring: move io_eventfd_put
      commit: 488a41100f4b9d7e10f05edead4e4d6d1c0c85a9
[6/7] io_uring: signal registered eventfd to process deferred task work
      commit: 3403692af0c6d5ae826f536a2c08f4e7c0b8b163
[7/7] io_uring: trace local task work run
      commit: 73100da58e5b1f6d8ba85e134463fb2aaca59978

Best regards,
-- 
Jens Axboe



      parent reply	other threads:[~2022-08-30 14:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 12:50 [PATCH for-next v4 0/7] io_uring: defer task work to when it is needed Dylan Yudaken
2022-08-30 12:50 ` [PATCH for-next v4 1/7] io_uring: remove unnecessary variable Dylan Yudaken
2022-08-30 12:50 ` [PATCH for-next v4 2/7] io_uring: introduce io_has_work Dylan Yudaken
2022-08-30 12:50 ` [PATCH for-next v4 3/7] io_uring: do not run task work at the start of io_uring_enter Dylan Yudaken
2022-08-30 12:50 ` [PATCH for-next v4 4/7] io_uring: add IORING_SETUP_DEFER_TASKRUN Dylan Yudaken
2022-08-30 12:50 ` [PATCH for-next v4 5/7] io_uring: move io_eventfd_put Dylan Yudaken
2022-08-30 12:50 ` [PATCH for-next v4 6/7] io_uring: signal registered eventfd to process deferred task work Dylan Yudaken
2022-08-30 12:50 ` [PATCH for-next v4 7/7] io_uring: trace local task work run Dylan Yudaken
2022-08-30 14:30 ` Jens Axboe [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 \
    --in-reply-to=166186982233.41433.18357763965407387116.b4-ty@kernel.dk \
    [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