Date: Sun, 21 Dec 2008 03:16:11 +0000 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: Network Stack Code Re-write (Possible motivations...?) Message-ID: <20081221031611.6f1dc764@gumby.homeunix.com> In-Reply-To: <441vw2zcdb.fsf@lowell-desk.lan> References: <1229788709.1583.16.camel@MGW_1> <44iqpezlb8.fsf@lowell-desk.lan> <20081220205414.A10042@wojtek.tensor.gdynia.pl> <448wqazfyf.fsf@lowell-desk.lan> <20081220224016.S10302@wojtek.tensor.gdynia.pl> <441vw2zcdb.fsf@lowell-desk.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 20 Dec 2008 17:54:24 -0500 Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> wrote: > However, > commercial routers generally do not use their OS kernel this way -- it > is far more common that the kernel does send and receive packets > within its native IP stack. If I'm understanding you right, I'm surprised by that (the native part). It make any proprietary software less portable. You're also tying your code into third-party internals, which sounds like a maintenance problem. I would have thought that the likes of Cisco and Alcatel etc would would have reusable codebases that abstract the OS and minimize OS dependencies. What's the advantage, don't routers usually lead OS's in terms of new protocol support?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081221031611.6f1dc764>