Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Dec 2008 22:41:13 +0100 (CET)
From:      Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>
To:        Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Network Stack Code Re-write (Possible motivations...?)
Message-ID:  <20081220224016.S10302@wojtek.tensor.gdynia.pl>
In-Reply-To: <448wqazfyf.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>

next in thread | previous in thread | raw e-mail | index | archive | help
>>> 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.
>
> It can be.  I've written portable IP stacks intended for exactly this
Of course it can. i just write that FreeBSD network stack WASN'T MADE for 
that.
not if it can or not.

>> routing ASIC's and put them there!
>
> Mostly, yes.  But the system still has to be network manageable.  That
> requires that it send and receive packets.  Doing so requires using the
> same routing information that the forwarding engines are using to
> forward packets in the same address space.  The kernel *does* still need
> to know routes to any of its destinations.

but kernel doesn't forward much packets.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081220224016.S10302>