From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET] io_uring: never block for block based IO submit
Date: Thu, 4 Jun 2020 11:48:28 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
We still have a case where resource starvation can cause us to block.
I've been running with a debug patch to detect cases where an io_uring
task can go uninterruptibly to sleep, and this is the main one.
This patchset provides a way for io_uring to have a holding area for
requests that should get retried, and a way to signal to the block stack
that we should be attempting to alloate requests with REQ_NOWAIT. When
we finish the block plug, we re-issue any requests that failed to get
allocated.
--
Jens Axboe
next reply other threads:[~2020-06-04 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 17:48 Jens Axboe [this message]
2020-06-04 17:48 ` [PATCH 1/4] block: provide plug based way of signaling forced no-wait semantics Jens Axboe
2020-06-04 17:48 ` [PATCH 2/4] io_uring: always plug for any number of IOs Jens Axboe
2020-06-04 17:48 ` [PATCH 3/4] io_uring: catch -EIO from buffered issue request failure Jens Axboe
2020-06-04 17:48 ` [PATCH 4/4] io_uring: re-issue plug based block requests that failed Jens Axboe
2020-06-05 3:20 ` [PATCH v2] " 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