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!
Looks good on a first read. Probably need to limit buffer ids to something < 32bit? Should the kernel check for non-uniqueness of ids?
-
-
Pushed update, now it works. No error checking is done yet, for length of buffer, group id, etc. So that needs doing, this is just provided for direction. I thought about the buffer id, and I think that's just up to the application. But I'm open to improvements.
-
Mostly commented on the buffer ids width bit because it's ABI. Wondering whether cqe.flags ought to be split into two parts. Perhaps that'd still be ok because there's no uses of it yet?
- 5 more replies
New conversation -
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.