| To: | "David S. Miller" <davem@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000 |
| From: | Nivedita Singhvi <niv@xxxxxxxxxx> |
| Date: | Thu, 5 Sep 2002 21:20:47 -0700 |
| Cc: | hadi@xxxxxxxxxx, tcw@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20020905.205842.127265672.davem@redhat.com> |
| References: | <Pine.GSO.4.30.0209052129580.21731-100000@shell.cyberus.ca> <1031283490.3d7823228d9ed@imap.linux.ibm.com> <20020905.205842.127265672.davem@redhat.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Internet Messaging Program (IMP) 3.0 |
Quoting "David S. Miller" <davem@xxxxxxxxxx>: > > ifconfig -a and netstat -rn would also be nice to have.. > > TSO gets turned off during retransmits/SACK and the card does not > do > retransmits. > > Can we move on in this conversation now? :-) Sure :). The motivation for seeing the stats though would be to get an idea of how much retransmission/SACK etc activity _is_ occurring during Troy's SpecWeb runs, which would give us an idea of how often we're actually doing segmentation offload, and better idea of how much gain its possible to further get from this(ahem) DMA coalescing :). Some of Troy's early runs had a very large number of packets dropped by the card. thanks, Nivedita |
| Previous by Date: | Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000, David S. Miller |
|---|---|
| Next by Date: | Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000, David S. Miller |
| Previous by Thread: | Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000, David S. Miller |
| Next by Thread: | Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |