Re: improved TSO interface needed

2007-02-26 Thread Andre Oppermann
Kip Macy wrote: 64K is the max, and I believe that is taking into account the headers. What size are you seeing that is larger? Even if an mbuf chain comes down that large, it does NOT form a single packet, it is packetized by the hardware into MTU size, as I said, on the wire, ie as the receive

Re: improved TSO interface needed

2007-02-26 Thread Andre Oppermann
Kip Macy wrote: LSO is MicroSlop's term for TSO :) As usual, they rename it, and next they do something non-standard to er 'differentiate' as the euphemism goes... Kinda what Sun's lawsuit back in the 90s against their Java strategy was all about :) Nevertheless, I don't understand Kip either,

Re: improved TSO interface needed

2007-02-25 Thread Kip Macy
64K is the max, and I believe that is taking into account the headers. What size are you seeing that is larger? Even if an mbuf chain comes down that large, it does NOT form a single packet, it is packetized by the hardware into MTU size, as I said, on the wire, ie as the receiver sees it, its ju

Re: improved TSO interface needed

2007-02-25 Thread Jack Vogel
On 2/25/07, Kip Macy <[EMAIL PROTECTED]> wrote: The stack will send down chains where pkthdr.len > 65536 bytes - I'm also seeing it send down mbuf chains of 66 mbufs or more. I don't think all cards can handle an arbitrary number of descriptors being used for a single packet. 64K is the max, a

Re: improved TSO interface needed

2007-02-25 Thread Jack Vogel
On 2/25/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: Kip Macy wrote: > On 2/25/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: >> Kip Macy wrote: >> > Evidently FreeBSD violates the LSO spec by sending down up to socket >> > buffer sized TSO segments to the network card. Is there a way to set >>

Re: improved TSO interface needed

2007-02-25 Thread Kip Macy
LSO is MicroSlop's term for TSO :) As usual, they rename it, and next they do something non-standard to er 'differentiate' as the euphemism goes... Kinda what Sun's lawsuit back in the 90s against their Java strategy was all about :) Nevertheless, I don't understand Kip either, when we do TSO th

Re: improved TSO interface needed

2007-02-25 Thread Andre Oppermann
Kip Macy wrote: On 2/25/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: Kip Macy wrote: > Evidently FreeBSD violates the LSO spec by sending down up to socket > buffer sized TSO segments to the network card. Is there a way to set > this other than reducing net.inet.tcp.sendbuf_max to a compliant

Re: improved TSO interface needed

2007-02-25 Thread Andre Oppermann
Kip Macy wrote: Evidently FreeBSD violates the LSO spec by sending down up to socket buffer sized TSO segments to the network card. Is there a way to set this other than reducing net.inet.tcp.sendbuf_max to a compliant value (64k)? And is there a way to for a device to communicate to the stack th

Re: improved TSO interface needed

2007-02-25 Thread Kip Macy
On 2/25/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: Kip Macy wrote: > Evidently FreeBSD violates the LSO spec by sending down up to socket > buffer sized TSO segments to the network card. Is there a way to set > this other than reducing net.inet.tcp.sendbuf_max to a compliant value > (64k)? An

improved TSO interface needed

2007-02-24 Thread Kip Macy
Evidently FreeBSD violates the LSO spec by sending down up to socket buffer sized TSO segments to the network card. Is there a way to set this other than reducing net.inet.tcp.sendbuf_max to a compliant value (64k)? And is there a way to for a device to communicate to the stack the maximum length