From: Pavel Begunkov <[email protected]>
To: Bikal Gurung <[email protected]>, [email protected]
Subject: Re: Confused about count argument in io_uring_prep_timeout
Date: Wed, 27 Jul 2022 11:44:37 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+v7nzg1O_nw6yicX9uVs7BpaovH7Z0hNgqzKrRLP-_m3XA-_g@mail.gmail.com>
On 7/27/22 11:20, Bikal Gurung wrote:
> Hi all,
>
> I am trying to understand the 'count' argument in liburing
> io_uring_prep_timeout call. Does this argument signify the number of
> cqes after which the timeout value 'ts' becomes armed?
Short answer, if you want just a timeout, i.e. will be triggered
according to the specified timespec if not cancelled, just set it
to 0.
TL;DR;
It's apparently a niche feature I'm not aware anyone is using, it
make the timeout request to complete when there has been added
@count or more CQEs since the timeout was queued. I'd love
to deprecate it tbh.
--
Pavel Begunkov
prev parent reply other threads:[~2022-07-27 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 10:20 Confused about count argument in io_uring_prep_timeout Bikal Gurung
2022-07-27 10:44 ` Pavel Begunkov [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 \
[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