From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET 0/5] io-wq fixes
Date: Thu, 2 Sep 2021 13:25:15 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
Got a report on io-wq stalls, and it turned into quite the rabbit hole
of fixes. There are two main things fixed by this series:
1) Single ring that has a lot of bounded vs unbounded traffic. The fix
is mainly just splitting the bounded and unbounded lists, so that we
never stall bounded unnecessarily. There are further cleanups possible
on top of this, but that should be deferred to 5.16.
2) Workloads that have io-wq work and rely heavily on signaling to
communicate between processes/threads. This can interfere with worker
creation, and this is particularly troublesome if it just happens to
occur with the first worker creation.
In general, harden the worker creation and ensure we handle failures in
terms of allocations and worker creations.
--
Jens Axboe
next reply other threads:[~2021-09-02 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 19:25 Jens Axboe [this message]
2021-09-02 19:25 ` [PATCH 1/5] io-wq: fix queue stalling race Jens Axboe
2021-09-02 19:25 ` [PATCH 2/5] io-wq: split bounded and unbounded work into separate lists Jens Axboe
2021-09-02 19:25 ` [PATCH 3/5] io-wq: only exit on fatal signals Jens Axboe
2021-09-02 19:25 ` [PATCH 4/5] io-wq: get rid of FIXED worker flag Jens Axboe
2021-09-02 19:25 ` [PATCH 5/5] io-wq: make worker creation resilient against signals 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] \
/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