Replies: 3 comments 5 replies
-
Makes sense indeed. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Thanks! What version it's gonna be merged to? |
Beta Was this translation helpful? Give feedback.
3 replies
-
Hi Jens, thank you!
…On Fri, Jan 12, 2024, 4:05 PM Jens Axboe ***@***.***> wrote:
Closed #1020 <#1020> as
resolved.
—
Reply to this email directly, view it on GitHub
<#1020>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4BFCEZGV7FC5JQGFO2U7LYOE7K7AVCNFSM6AAAAABA3KMCMCVHI2DSMVQWIX3LMV45UABFIRUXGY3VONZWS33OIV3GK3TUHI5E433UNFTGSY3BORUW63R3GEYDINZQGYZA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
similarly to
io_uring_cq_ready
could be nice to have a method returning number of buffers unclaimed yet by the kernel, i.e. those that need to be released byio_uring_buf_ring_advance
. One possible application for that - for tests, to make sure the application code has released back the buffers it consumed.Beta Was this translation helpful? Give feedback.
All reactions