I'm missing some "high level" context about io_uring, I might as well ask here:
- If I want to write a multithreaded program, is it best to have one io_uring per thread?
- Per CPU core?
- Per device or PCIe lane to the device? (It might make sense ...)
- Or one for the whole program? (Will Linux distribute requests across cores and run them in parallel for me?)
- If I'm writing a library that uses io_uring, should I create my own io_uring or offer an interface to add requests to one which the main program creates? (Or perhaps both?)
const grent = match (passwd::getgroup(group)) {
void => fmt::fatal("No '{}' group available", group),
gr: passwd::grent => gr,
};
For confused people: it's written in author's language Hare. The language uses QBE as backend [2]. I wonder what author has against Zig (probably at least current dependence on LLVM). It reminds me of Myrddin [3], which AFAIR is connected to Suckless folks.
I tried to use finger in Ubuntu, and it doesn't display UTF-8 correctly. It seems that a patch would fix this but it's been untouched for 6 years https://bugs.launchpad.net/ubuntu/+source/bsd-finger/+bug/46...