Date: Mon, 23 Aug 2010 21:27:10 -0600 From: Chad Perrin <perrin@apotheon.com> To: freebsd-questions@freebsd.org Subject: Re: Why is the FreeBSD TCP/IP stack the best? Message-ID: <20100824032710.GC65931@guilt.hydra> In-Reply-To: <AANLkTin4opE66SZdBLgPqu3Hso5fW8DZPGSVNxsRZ_KE@mail.gmail.com> References: <AANLkTin4opE66SZdBLgPqu3Hso5fW8DZPGSVNxsRZ_KE@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--7qSK/uQB79J36Y4o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Perhaps they rely on the opinions of other OSes' developers -- many of whom have borrowed FreeBSD TCP/IP code to bootstrap their own network stacks. Of course, I think a number of factors contribute to this without necessarily proving it is the technical "best": * BSD Unix was first out the gate in the race to TCP/IP. * FreeBSD uses the BSD License, which makes its code easy to reuse. * Developers for the various open source BSD Unix systems tend to have a high regard for "correctness". * I haven't looked at it personally, but have heard that FreeBSD's TCP/IP stack source code is quite clean and readable -- and therefore easily reused. There may be other reasons involved. FreeBSD does tend to rate fairly well in network performance benchmarks, by the way, but those benchmarks are not typically tuned for testing the TCP/IP stack *specifically*, from what I've seen. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --7qSK/uQB79J36Y4o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkxzPA4ACgkQ9mn/Pj01uKUB5QCgk79OzE/+4v6hkfHtm4zT4YoX aWkAoKQXAzaIUtrTPPS0ym0ZHuVzVxF5 =U5HK -----END PGP SIGNATURE----- --7qSK/uQB79J36Y4o--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100824032710.GC65931>