From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] CQ-seq only based timeouts
Date: Sat, 30 May 2020 14:54:16 +0300 [thread overview]
Message-ID: <cover.1590839530.git.asml.silence@gmail.com> (raw)
The old series that makes timeouts to trigger exactly after N
non-timeout CQEs, but not (#inflight + req->off).
v2: variables renaming
v3: fix ordering with REQ_F_TIMEOUT_NOSEQ reqs
squash 2 commits (core + ingnoring timeouts completions)
extract a prep patch (makes diffs easier to follow)
Pavel Begunkov (2):
io_uring: move timeouts flushing to a helper
io_uring: off timeouts based only on completions
fs/io_uring.c | 97 ++++++++++++++-------------------------------------
1 file changed, 27 insertions(+), 70 deletions(-)
--
2.24.0
next reply other threads:[~2020-05-30 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 11:54 Pavel Begunkov [this message]
2020-05-30 11:54 ` [PATCH v3 1/2] io_uring: move timeouts flushing to a helper Pavel Begunkov
2020-05-30 11:54 ` [PATCH v3 2/2] io_uring: off timeouts based only on completions Pavel Begunkov
2020-05-30 13:50 ` [PATCH v3 0/2] CQ-seq only based timeouts 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=cover.1590839530.git.asml.silence@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.