Re:Why do we use the Linux kernel's TCP stack? (2016)
by maartenh on Sunday October 04, 2020 @06:37AM
(#24677855)
How would you debug programs using ioring? With the traditional I/O syscalls, one can use tools like strace to observe the behavior of a program.
Would using BPF to instrument the ioring be the way to go?
Re:Why do we use the Linux kernel's TCP stack? (2016)
by bogomipz on Saturday October 03, 2020 @06:12PM
(#24675064)
>"I'd expect more future uses of xdp over dpdk."
Can say why that is? I haven't really kept up with DPDK but I know there was lots of interest in it a few years back. What has changed?
Re:Why do we use the Linux kernel's TCP stack? (2016)
by wtallis on Sunday October 04, 2020 @01:30AM
(#24676716)
I haven't been watching the networking side too closely, but I expect the same thing to play out for storage with io_uring vs SPDK. When the in-kernel solution is almost as fast, has much broader availability and compatibility, and imposes fewer constraints on hardware purchasing decisions and system administration, the userspace offload solution gets consigned to a fairly small niche.
Re:Why do we use the Linux kernel's TCP stack? (2016)
by brendangregg on Sunday October 04, 2020 @02:01AM
(#24676828)
Right; there's a better presentation I can't find right now, but here's one from Intel showing how XDP was catching up in 2018 http://vger.kernel.org/lpc_net2018_talks/lpc18_pres_af_xdp_p...
And that poses a problem: to reach maximum performance requires many engineering hours to learn and configure all of these. You'd need a large gain to justify doing this: E.g., for a system doing over 1M packets/s.
This complexity may change. Look at BPF for observability: we built BCC and bpftrace so that using it was trivial. What trivial front-end/technology could we build upon XDP and io_uring to make deployment easy?