Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Behavior of io_uring_wait_cqes is not documented for null ts #1209

Open
travisdowns opened this issue Aug 19, 2024 · 1 comment
Open

Behavior of io_uring_wait_cqes is not documented for null ts #1209

travisdowns opened this issue Aug 19, 2024 · 1 comment

Comments

@travisdowns
Copy link

It does not seem to be documented what the behavior of io_uring_wait_cqes when ts is NULL. It is implicitly allowed to be NULL by "If ts is specified and an older kernel without..." but it isn't clear what happens. Is it an infinite timeout or no timeout (like peek) or something else?
@axboe
Copy link
Owner

axboe commented Aug 19, 2024

Like any of the timeout functions, if NULL is given it's an infinite timeout.

axboe added a commit that referenced this issue Aug 19, 2024
@axboe
man: note that a NULL pointer timeout always means "wait forever"
1ecfda1 
Link: #1209
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@travisdowns @axboe