6 ms·
Why Linux? The networking stack on BSD is superior, and the OS places no copyleft restrictions! I'm starting to believe that developers choose OS/Tools the are
by mankash666 11y ago
Why Linux? The networking stack on BSD is superior, and the OS places no copyleft restrictions!
I'm starting to believe that developers choose OS/Tools the are used to (Linux in this case) versus the one best suited for the job (BSD)
- untog 11y ago> I'm starting to believe that developers choose OS/Tools the are used to (Linux in this case) versus the one best suited for the job (BSD) They do, and it isn't always the wrong choice. If you know the OS inside out it's better to use that than a brand new one you don't know the sharp edges of yet.
- iheredia 11y agoWhich tool is the best for a task is not always the major factor. Other things like the developer team experience with the tools, the community support and the planned deadlines sometimes makes the decision a little harder. If the ms teams are already familiar with tweaking linux distros to their needs, then it seems like a good choise
- geographomics 11y agoIn what ways is the BSD networking stack superior?
- bladerunner82 11y agoThroughput. The BSD networking stack has been very carefully engineered over time. Linux is OK, but nowhere near as robust. FreeBSD is legendary for load tolerance and network throughput, that on equal machines would choke a Linux server. Seen it, work(ed) with it. When we do something serious that requires heavy load and awesome throughput, we always lean on FreeBSD, never anything else. Everything else has always let us down.
- mixmastamyk 11y agoThat was as true ten years ago, is it still? Have there been any recent benchmarks?
- derefr 11y agoI know that a bit more recently (~4 years ago) WhatsApp emphasized that FreeBSD's networking stack was part of what allowed them to scale so cheaply. I'm sure there was a good amount of benchmarking and profiling involved in that choice, using their production workloads.
- deleted 11y ago[deleted]
- saosebastiao 11y agoI've seen this claim before, but I've also seen the counterclaim that Linux network stacks have since caught up and even surpassed the BSDs on throughput and latency. Whether one or the other is truly better though might be irrelevant...either is such a monumental improvement over the windows networking stack that there are bound to be large benefits.
- detaro 11y agoThis is an OS for the control plane for hardware switches, so its throughput is not that important. Hardware does most of the heavy lifting.
- bladerunner82 11y agoI understand this, but was answering the question (in general) about why I believe BSD has better networking.
- Nux 11y agoHad mediocre network performance and increased load with freebsd on VMs (kvm), while at the same time a linux one would saturate a whole link.
- cyphar 11y agoWhy are you trying to get network throughput on a VM? Of course it's going to be slow, but KVM probably has some passthrough optimisations for Linux guests.
- nl 11y agoBecause that's what software defined networking is (mostly) about. In the majority of cases it's used as a way to setup a network plane for virtualized hosts. Edit: See for example why VMWare bought Nicira: http://techcrunch.com/2012/07/23/vmware-buys-nicira-for-1-26-billion-and-gives-more-clues-about-cloud-strategy/ http://techcrunch.com/2012/07/23/vmware-buys-nicira-for-1-26...
- cyphar 11y agoI'm not a BSD guy, but I can still see it's a little unfair to compare the network throughputs of Linux and *BSD as guest VMs on a Linux host running KVM. You aren't going to get good throughout in that case without hardware passthrough (even then it's still bad). End of story.
- chris_wot 11y agoNot that I really doubt you (the FreeBSD developers have a hard won and worthy reputation in this area!) but do you have any benchmarks that help back this claim? I promise this isn't a question to try to make a point, I'm genuinely interested.
- DevOpsTiger 11y agoBenchmarks please, thank you!
- davidgerard 11y agoGot benchmark numbers on that?
- m-app 11y agoExcept that in this case it doesn't matter. The real forwarding is done in the ASIC's of the switches.
- nl 11y agoBecause the hardware[1] mostly is only supported on Linux, or the Linux support is more mature. Take the Cavium products: they shipped multiple distributions of Linux on the Arm64 products 2+ years ago, and FreeBSD around 18 months later. The Juniper products only support Linux. [1] http://www.opencompute.org/wiki/Networking/SpecsAndDesigns http://www.opencompute.org/wiki/Networking/SpecsAndDesigns
- cyphar 11y ago> ... and the OS places no copyleft restrictions! I'm still baffled why people think this is a benefit. If you actually care about software freedom, lack of copyleft is a bad thing IMO. What's to stop $EvilCorp from creating a system that is completely locked down, can't be replaced, and is based on your technology? That's what UEFI is, by the way. It's only by Microsoft's blessing that you can install alternative operating systems on new Windows laptops. So please tell me more about why copyleft is a negative. If TianoCore was GPLv3, UEFI would actually be more bearable to work with (but core/libreboot is clearly the way to go on from here).
- deleted 11y ago[deleted]
- chei0aiV 11y agoFYI, the TianoCore FAT driver is actually non-free thanks to Microsoft.
- cyphar 11y agoActually, Microsoft has provided a patent grant[1][2][3] to anybody who implements a FAT driver for the purpose of booting UEFI. Which is actually a reason why FAT is still in the Linux kernel even though people argue that Microsoft will sue one day. But IMO we should be all switching to CoreBoot (or LibreBoot). It's much less fucked up than UEFI, the only negative being that you have to flash it yourself (unless you buy a $1000 5-year-old Thinkpad). [1]: http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/fatgen103.doc http://download.microsoft.com/download/1/6/1/161ba512-40e2-4...
- chei0aiV 11y agoThey are still responsible for the non-free license on the TianoCore; Intel are having to negotiate with Microsoft to change the license, despite being the copyright holder. Agreed re not using UEFI. I wouldn't touch CoreBoot though, LibreBoot seems more sane.