On Sat, 25 Aug 2007, Herbert Xu wrote:
> On Fri, Aug 24, 2007 at 02:25:03PM -0700, David Miller wrote:
> >
> > My hunch is that even if in the non-TSO case the TX packets were all
> > back to back in the cards TX ring, TSO still spits them out faster on
> > the wire.
>
> If this is the case then we should see an improvement by
> disabling TSO and enabling GSO.
TSO disabled and GSO enabled:
[EMAIL PROTECTED] redhat]# nuttcp -w10m 192.168.88.16
11806.7500 MB / 10.00 sec = 9900.6278 Mbps 100 %TX 84 %RX
[EMAIL PROTECTED] redhat]# nuttcp -M1460 -w10m 192.168.88.16
4872.0625 MB / 10.00 sec = 4085.5690 Mbps 100 %TX 64 %RX
In the "-M1460" case, there was generally less receiver CPU utilization,
but the transmitter utilization was generally pegged at 100 %, even
though there wasn't any improvement in throughput compared to the
TSO enabled case (in fact the throughput generally seemed to be somewhat
less than the TSO enabled case). Note there was a fair degree of
variability across runs for the receiver CPU utilization (the one
shown I considered to be representative of the average behavior).
Repeat of previous test results:
TSO enabled and GSO disabled:
[EMAIL PROTECTED] ~]# nuttcp -w10m 192.168.88.16
11813.4375 MB / 10.00 sec = 9906.1644 Mbps 99 %TX 80 %RX
[EMAIL PROTECTED] ~]# nuttcp -M1460 -w10m 192.168.88.16
5102.8503 MB / 10.06 sec = 4253.9124 Mbps 39 %TX 99 %RX
TSO disabled and GSO disabled:
[EMAIL PROTECTED] ~]# nuttcp -w10m 192.168.88.16
11818.2500 MB / 10.00 sec = 9910.0176 Mbps 100 %TX 78 %RX
[EMAIL PROTECTED] ~]# nuttcp -M1460 -w10m 192.168.88.16
5399.5625 MB / 10.00 sec = 4527.9070 Mbps 99 %TX 76 %RX
-Bill
-
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
