Seems like it'd be a shame to have the polled/async improvements and not include automatic buffer selection. I guess that'll be the Sunday project.
IORING_OP_BUFFER_FREE suggests that buffers are registered somehow (?). How about instead having an explicit opcode that provides a buffer for a one-off use? A IORING_OP_PROVIDE_BUFFER registers a buffer as available, with buf_index (under different name) indicating a 'group'.
-
-
Question is where that buffer comes from, my current code is having the app provide them (upfront). Kernel selects one (for IOSQE_BUFFER_SELECT), and IORING_OP_BUFFER_FREE marks that buffer as free again.
-
Was thinking that buffers are provided one-off, not permanently. So you'd have to IORING_OP_PROVIDE_BUFFER once for each buffer ahead of time, and then *again* after used by kernel and consumed by userland. Don't see a lot of benefit of permanent in kernel registry.
- 13 more replies
New conversation -
-
-
And a IORING_OP_RECVMSG can flag use of a group with something like IOSQE_PROVIDED_BUFFER, and buf_index indicating the group.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.