Ten years with DragonFly BSD network stack [pdf]
leaf.dragonflybsd.org
leaf.dragonflybsd.org
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.
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?
https://www.dragonflybsd.org/features/
and here:
3. The parts of the DragonFlyBSD’s net-work stack that can really enjoy help hands.
...
- The IPv6 stack; though I am making progress, the progress is slow.
Ouch. I'm guessing this means IPv6 is just slow and not that it doesn't work at all, but it seems like something that's going to be a problem in a couple of years.He's not saying IPv6 network performance is slow, he's saying he doesn't have as much time as he'd like to work on it.
http://lists.dragonflybsd.org/pipermail/users/2017-March/313...
Submitted it a couple of weeks ago but it never reached the frontpage