News for hackers. Stuff that matters.
Re:Basic proxy implementation using io_uring by lukeh on Sunday February 18, 2024 @02:16AM (#39416921)
I’m using it for all I/O (file, socket, SPI and UART) in an embedded application written in Swift. Wrappers here:

https://github.com/PADL/IORingSwift

Re:Basic proxy implementation using io_uring by MrBuddyCasino on Sunday February 18, 2024 @06:35AM (#39418242)
What type of app can afford to run on Linux (not bare metal) but still needs such low level performance optimizations?
Re:Basic proxy implementation using io_uring by surajrmal on Sunday February 18, 2024 @07:34AM (#39418529)
Lowering CPU usage can save battery. Just because you are running Linux doesn't mean you don't have a power budget.
Re:Basic proxy implementation using io_uring by p_l on Sunday February 18, 2024 @07:50AM (#39418608)
Among many other projects I touched, we had a database engine which planned to move to io_uring as soon as it could be made available (it wasn't distributed outside company, so it was a question of internal infrastructure)

PREEMPT_RT also includes a lot of possible low-latency work.

io_uring also provides ridiculous performance benefits for normal server code, too.

Re:Basic proxy implementation using io_uring by sophacles on Sunday February 18, 2024 @03:00PM (#39422535)
Context switches are expensive. Often more expensive than operating on the data. io_uring providews a major reduction, or even near elimination of context swithes for io. It provides big win in a lot of server contexts in terms of packets/iops/throughput.
Re:Basic proxy implementation using io_uring by lukeh on Monday February 19, 2024 @03:13AM (#39427253)
Initial motivation was lack of non-blocking SPI I/O in Linux user space. Then it made sense to use it for everything, it’s a straightforward mapping to Swift’s structured concurrency, so why not?