From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, David Wei <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v4] io_uring: add support for multishot timeouts
Date: Tue, 18 Apr 2023 19:39:11 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 18 Apr 2023 15:58:18 -0700, David Wei wrote:
> A multishot timeout submission will repeatedly generate completions with
> the IORING_CQE_F_MORE cflag set. Depending on the value of the `off'
> field in the submission, these timeouts can either repeat indefinitely
> until cancelled (`off' = 0) or for a fixed number of times (`off' > 0).
>
> Only noseq timeouts (i.e. not dependent on the number of I/O
> completions) are supported.
>
> [...]
Applied, thanks!
[1/1] io_uring: add support for multishot timeouts
commit: ea97f6c8558e83cb457c3b5f53351e4fd8519ab1
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-04-19 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 22:58 [PATCH v4] io_uring: add support for multishot timeouts David Wei
2023-04-19 1:39 ` 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=168186835123.340981.13070185209888390249.b4-ty@kernel.dk \
[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