From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org
Cc: peterz@infradead.org, mingo@kernel.org
Subject: [PATCHSET v2 0/2] Replace io_uring workqueues with io-wq
Date: Fri, 25 Oct 2019 11:22:49 -0600 [thread overview]
Message-ID: <20191025172251.12830-1-axboe@kernel.dk> (raw)
Hopefully the sched core changes are palatable. io-wq uses the same
sched in/out hooks as workqueue, and if the task isn't either a
workqueue or io-wq worker, there should be no extra overhead there.
Patches are on top of my for-5.5/io_uring branch, and can also be found
here:
http://git.kernel.dk/cgit/linux-block/log/?h=for-5.5/io_uring-wq
This passes io_uring IO testing and repeated runs of the liburing
regressions suite, and passes tests that would previously deadlock.
Also see LWN article here:
https://lwn.net/Articles/803070/
Changes since v1:
- Fix dependent work hash
- Turn wqe->state into wqe->flags
- Fix issue with unusing mm/files if worker got busy at exit timo
- Fix issue with hashed work bit mangling (Colin)
- Fix issue with dependent work
- Rebase
fs/Kconfig | 3 +
fs/Makefile | 1 +
fs/io-wq.c | 805 ++++++++++++++++++++++++++++++++
fs/io-wq.h | 55 +++
fs/io_uring.c | 414 ++++------------
include/linux/sched.h | 1 +
include/trace/events/io_uring.h | 12 +-
init/Kconfig | 1 +
kernel/sched/core.c | 16 +-
9 files changed, 981 insertions(+), 327 deletions(-)
--
Jens Axboe
next reply other threads:[~2019-10-25 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 17:22 Jens Axboe [this message]
2019-10-25 17:22 ` [PATCH 1/2] io-wq: small threadpool implementation for io_uring Jens Axboe
2019-10-28 17:10 ` Peter Zijlstra
2019-10-28 21:21 ` Jens Axboe
2019-10-25 17:22 ` [PATCH 2/2] io_uring: replace workqueue usage with io-wq 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=20191025172251.12830-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.