Ingo,
I looked through some of the Tux docs and stuff over the weekend. You
are correct, it looks an awful lot like the Topology Support Module
Layer in NetWare, and I agree it provides very similiar semantics. I
won't know how Alan's code stacks up against NetWare until I complete
the port, but I think we will see performance at least equal to Native
NetWare if we include your tux stuff with it.
Jeff
Ingo Molnar wrote:
>
> On Sat, 2 Sep 2000, Jeff V. Merkey wrote:
>
> > **ALL** Netware network drivers support a scatter/gather proramming
> > interface, whether the hardware does or not. In NetWare, the drivers
> > get passed a fragment list in what's called an ECB (Event Control
> > Block). It's the drivers responsiblity to assemble the fragment lists.
> > We did it this way to support scatter/gather cards and non-scatter
> > gather cards in one interface. Those drivers that do not support
> > scatter gather DMA operations copy to a local buffer to assemble the
> > packet. [...]
>
> this is exactly what TUX implements and what i mentioned in my first email
> that started this thread. Was a complete overhaul of the TCP/IP stack
> needed like you claim? Not at all - the Linux TCP/IP code was so generic,
> that to my surprise i saw the first zero-copy TCP transfer after only one
> day of hacking.
>
> Ingo
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
