Date: Sat, 20 Dec 2008 20:55:42 +0100 (CET) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Cc: martes@mgwigglesworth.com, freebsd-questions@freebsd.org Subject: Re: Network Stack Code Re-write (Possible motivations...?) Message-ID: <20081220205414.A10042@wojtek.tensor.gdynia.pl> In-Reply-To: <44iqpezlb8.fsf@lowell-desk.lan> References: <1229788709.1583.16.camel@MGW_1> <44iqpezlb8.fsf@lowell-desk.lan>
index | next in thread | previous in thread | raw e-mail
> I very much doubt that marketing issues were a significant issue. > Off-the-shelf OS networking has always fallen short of supporting it wasn't made for that. > As someone else already mentioned in this thread, supporting hardware > offload for forwarding is a major issue. Core routers (or even > provider-edge routers) depend on most of the packet forwarding being > done in proprietary hardware. Operating system IP stacks don't support > this very well; all of the routers I've worked on used the kernel IP > stack only for packets going to and from the kernel itself, and used a > different stack for what I call "transit" packets -- those that are > only being forwarded by the local system. as higher speed routers are "hardware" - why OS has to do ANY work on routing? it's just there to prepare routing tables in format required for routing ASIC's and put them there!home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081220205414.A10042>