It'd be kinda awesome if we could have an io_uring with multiple submission queues/rings, but only one completion queue/ring. With the ability to map the submission queue only in one process, but the completion queue in multiple.
CC: @axboe
-
Show this thread
-
Replying to @AndresFreundTec
Agree, it would be pretty nifty! Would not be hard to do, I think the hardest part would actually be the liburing side of it.
1 reply 0 retweets 2 likes -
Replying to @axboe
If it'd require more manual work to set up, it'd be fair enough. Though it turns out that the contention I was just seeing was unnecessary. Still bothersome to have to be careful to hold submission side lock until all submissions have to be consumed by kernel (due to mm/fds).
1 reply 0 retweets 0 likes -
Replying to @AndresFreundTec
It'd be trivial to ensure things are correct and eliminate any need to think about locking, which is always a win on the application side imho. I'll have to think about it a bit.
2 replies 0 retweets 1 like -
Replying to @axboe
I wonder if an alternative could be an IORING_REGISTER_PROCESS_CONTEXT. If specified mm/file/.. would reference that rather than the process invoking io_uring_enter().
1 reply 0 retweets 0 likes
Would make sqthread less painful to use too...
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.