Ron,
Didn't see you at FreeBSDcon..
Som if it's on the card how do you do things like ipfw?
And how do you route between cards?
Who keeps the routing table?
how does routed (or whatever) communicate with it?
how do you set tcp options?
you can do all these but it get's really complicated..
You have to associate a socket (even on win-nt) in the OS with a session
on the card..
The approach works if you have some very specialised applications but
if you're talking General purpose systems...
On Fri, 22 Oct 1999, Mike Smith wrote:
> > I'm wondering if anyone in this group has done or knows of a good profile
> > of a tcp send going from user mode to bits on the wire. Reason I'm asking
> > is the old "put TCP/IP on the NIC" is once again rearing its head, and I'm
> > hoping there are numbers I can point to (ones that aren't old, that is)
> > about why this may not be the best idea in the world. FreeBSD seems a good
> > choice since it has a pretty reasonable implementation.
>
> I'd start with "the NIC will require insane amounts of memory to deal
> with links with large bandwidth/delay products". And when people tell
> you that the NIC can just use system memory, you should slap them
> around the head. The thought of a piece of hardware screwing with the
> kernel memory allocator gives me the creeps. 8)
>
> --
> \\ Give a man a fish, and you feed him for a day. \\ Mike Smith
> \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
> \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
