From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nivedita Singhvi Subject: Re: Early SPECWeb99 results on 2.5.33 with TSO on e1000 Date: Thu, 5 Sep 2002 20:38:10 -0700 Sender: netdev-bounce@oss.sgi.com Message-ID: <1031283490.3d7823228d9ed@imap.linux.ibm.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Troy Wilson , linux-kernel@vger.kernel.org, netdev@oss.sgi.com Return-path: To: jamal In-Reply-To: Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org Quoting jamal : > I am not sure; if he gets a busy system in a congested network, i > can see the offloading savings i.e i am not sure if the amortization > of the calls away from the CPU is sufficient enough savings if it > doesnt involve a lot of retransmits. I am also wondering how smart > this NIC in doing the retransmits; example i have doubts if this > idea is briliant to begin with; does it handle SACKs for example? do you mean sack data being sent as a tcp option? dont know, lots of other questions arise (like timestamp on all the segments would be the same?). > Troy, i am not interested in the nestat -s data rather the TCP > stats this NIC has exposed. Unless those somehow show up magically > in netstat. most recent (dont know how far back) versions of netstat display /proc/net/snmp and /proc/net/netstat (with the Linux TCP MIB), so netstat -s should show you most of whats interesting. Or were you referring to something else? ifconfig -a and netstat -rn would also be nice to have.. thanks, Nivedita