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.
-
Show this thread
-
I have this working now, but I'm not sure how best to handle buffer life times. IOW, kernel selects a free buffer, but userspace needs to signal when it can be reused. I'm thinking a specific opcode for that, IORING_OP_BUFFER_FREE or something. Taking suggestions and/or advice!
1 reply 1 retweet 1 likeShow this thread -
I kind of like the opcode idea, as let's say you do a recv() and a buffer is selected. Presumably you're going to use that for a send or write, and you could link the IORING_OP_BUFFER_FREE command after that.
2 replies 0 retweets 1 likeShow this thread -
Replying to @axboe
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'.
2 replies 0 retweets 0 likes
And a IORING_OP_RECVMSG can flag use of a group with something like IOSQE_PROVIDED_BUFFER, and buf_index indicating the group.
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.