News for hackers. Stuff that matters.
Re:Ten years with DragonFly BSD network stack [pdf] by paws on Wednesday March 15, 2017 @04:01PM (#13879275)
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

Re:Ten years with DragonFly BSD network stack [pdf] by f2f on Wednesday March 15, 2017 @04:14PM (#13879372)
Literally 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.
Re:Ten years with DragonFly BSD network stack [pdf] by X86BSD on Wednesday March 15, 2017 @04:50PM (#13879646)
Yeah I believe Matt forked FreeBSD 4.x to start dragonfly.
Re:Ten years with DragonFly BSD network stack [pdf] by paws on Wednesday March 15, 2017 @06:24PM (#13880436)
I 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?

Re:Ten years with DragonFly BSD network stack [pdf] by sigzero on Wednesday March 15, 2017 @06:38PM (#13880542)