* Confused about count argument in io_uring_prep_timeout
@ 2022-07-27 10:20 Bikal Gurung
2022-07-27 10:44 ` Pavel Begunkov
0 siblings, 1 reply; 2+ messages in thread
From: Bikal Gurung @ 2022-07-27 10:20 UTC (permalink / raw)
To: io-uring
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?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Confused about count argument in io_uring_prep_timeout
2022-07-27 10:20 Confused about count argument in io_uring_prep_timeout Bikal Gurung
@ 2022-07-27 10:44 ` Pavel Begunkov
0 siblings, 0 replies; 2+ messages in thread
From: Pavel Begunkov @ 2022-07-27 10:44 UTC (permalink / raw)
To: Bikal Gurung, io-uring
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-07-27 10:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-07-27 10:20 Confused about count argument in io_uring_prep_timeout Bikal Gurung
2022-07-27 10:44 ` Pavel Begunkov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox