4 ms·
If anyone could summarize what makes DragonFly's stack different I'd be obliged. I understand FreeBSD's networking stack has been well-regarded since the 90s[1
by paws 10y ago
If anyone could summarize what makes DragonFly's stack different I'd be obliged.
I understand FreeBSD's networking stack has been well-regarded since the 90s[1] and has shipped in many environments and consumer devices. Now that it's 2017, it's interesting to see what else is out there.
[1] https://people.freebsd.org/~andre/tcpoptimization.html https://people.freebsd.org/~andre/tcpoptimization.html
- f2f 10y agoLiterally the entire section 2 of the linked to file discusses exactly what you're interested to know. It details the evolution of the DragonFlyBSD's network stack, which started as the FreeBSD network stack.
- X86BSD 10y agoYeah I believe Matt forked FreeBSD 4.x to start dragonfly.
- paws 10y agoI saw that, cheers. I'm more interested in the higher level takeaway. Why should developers use Dragonfly? Don't get me wrong, I appreciate the ability to peruse the kernel implementation narrative in the first place. As I'm not a kernel developer I'm left wondering what it means. e.g. better multicore performance?
- sigzero 10y agoI would look here: https://www.dragonflybsd.org/features/ https://www.dragonflybsd.org/features/ and here: https://www.dragonflybsd.org/performance/ https://www.dragonflybsd.org/performance/