←back to thread

lsr: ls with io_uring

(rockorager.dev)
335 points mpweiher | 1 comments | 18 Jul 25 12:40 UTC | HN request time: 0.511s | source
Show context
SillyUsername ◴[18 Jul 25 13:13 UTC] No.44604307[source]▶
Love it.

I'm trying to understand why all command line tools don't use io_uring.

As an example, all my nvme's on usb 3.2 gen 2 only reach 740MB/s peak.

If I use tools with aio or io_uring I get 1005MB/s.

I know I may not be copying many files simultaneously every time, but the queue length strategies and the fewer locks also help I guess.

replies(9): >>44604401 #>>44604434 #>>44604490 #>>44604735 #>>44604738 #>>44604905 #>>44605976 #>>44607467 #>>44608653 #
elcapitan ◴[18 Jul 25 14:01 UTC] No.44604735[source]▶
iirc io_uring also had some pretty significant security issues early on (a couple of years ago). Those should be fixed by now, but that probably dampened adoption as well.
replies(2): >>44606179 #>>44608434 #
1. raesene9 ◴[18 Jul 25 18:53 UTC] No.44608434[source]▶
Last I checked it's blocked by most container runtimes exactly because of the security problems, and Google blocked io_uring across all their services. I've not checked recently if that's still the case, but https://security.googleblog.com/2023/06/learnings-from-kctf-... has some background.