Chris Leech wrote:
When it says "buffer size" for the Chariot stuff, is that the socket
buffer size, or the size of the buffer(s) being passed to the transport?
That's the I/O size for the application, being passed to the transport.
Was the MTU 1500 or 9000 bytes?
1500 byte MTU
Can the Chariot do small packet latency tests and/or aggregate small
packet performance?
Yes, but for small I/O the overhead of pinning pages and initiating
the offloaded copy overtakes the benefits. We currently see that
cutoff at about 2k.
I must be missing something - if the MTU was 1500 bytes, how did the
receiver's offloaded copies get to the 2k level? Were several arriving
TCP segments aggregated?
thanks,
rick jones
- Chris
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
