From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com, jheffner@psc.edu, herbert@gondor.apana.org.au
Subject: Re: Current 2.6.x TSO state
Date: Fri, 1 Oct 2004 12:11:23 +0200 [thread overview]
Message-ID: <20041001121123.19511403.ak@suse.de> (raw)
In-Reply-To: <20040930213221.06a3f5b3.davem@davemloft.net>
On Thu, 30 Sep 2004 21:32:21 -0700
"David S. Miller" <davem@davemloft.net> wrote:
>
> 1) Andi sees performance anomaly to 2.6.5 kernels.
> Hopefully fixed by diff3 above, merely awaiting
> retesting by him.
Didn't fix the problem unfortunately, it's even a bit slower
with TSO than the previous kernel I tested.
The stretch acks are still quite visible, see
http://www.firstfloor.org/~andi/tso-stretch-ack1.gz for the full
log.
I will try to do the ACK instrumentation on the receiver you suggested
later, unfortunately have some other urgent things to do first.
Do you want me to play with the new sysctl too?
tcptrace output for the last run as overview:
complete conn: yes
first packet: Fri Oct 1 12:02:39.725840 2004
last packet: Fri Oct 1 12:02:49.729142 2004
elapsed time: 0:00:10.003302
total packets: 315102
filename: /tmp/LOG
e->f: f->e:
total packets: 298495 total packets: 16607
ack pkts sent: 298494 ack pkts sent: 16607
pure acks sent: 2 pure acks sent: 16605
unique bytes sent: 432215424 unique bytes sent: 0
actual data pkts: 298492 actual data pkts: 0
actual data bytes: 432215424 actual data bytes: 0
rexmt data pkts: 0 rexmt data pkts: 0
rexmt data bytes: 0 rexmt data bytes: 0
outoforder pkts: 0 outoforder pkts: 0
pushed data pkts: 16715 pushed data pkts: 0
SYN/FIN pkts sent: 1/1 SYN/FIN pkts sent: 1/1
req 1323 ws/ts: Y/Y req 1323 ws/ts: Y/Y
adv wind scale: 2 adv wind scale: 0
req sack: Y req sack: Y
sacks sent: 0 sacks sent: 0
mss requested: 1460 bytes mss requested: 1460 bytes
max segm size: 1448 bytes max segm size: 0 bytes
min segm size: 456 bytes min segm size: 0 bytes
avg segm size: 1447 bytes avg segm size: 0 bytes
max win adv: 5840 bytes max win adv: 63712 bytes
min win adv: 5840 bytes min win adv: 5792 bytes
zero win adv: 0 times zero win adv: 0 times
avg win adv: 5840 bytes avg win adv: 63673 bytes
initial window: 4344 bytes initial window: 0 bytes
initial window: 3 pkts initial window: 0 pkts
ttl stream length: 432215424 bytes ttl stream length: 0 bytes
missed data: 0 bytes missed data: 0 bytes
truncated data: 423260664 bytes truncated data: 0 bytes
truncated packets: 298492 pkts truncated packets: 0 pkts
data xmit time: 10.003 secs data xmit time: 0.000 secs
idletime max: 8.4 ms idletime max: 8.6 ms
throughput: 43207275 Bps throughput: 0 Bps
No SACKs etc.
-Andi
next prev parent reply other threads:[~2004-10-01 10:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 4:32 Current 2.6.x TSO state David S. Miller
2004-10-01 10:11 ` Andi Kleen [this message]
2004-10-01 19:47 ` David S. Miller
2004-10-01 19:51 ` Andi Kleen
2004-10-01 19:56 ` David S. Miller
2004-10-01 20:01 ` Andi Kleen
2004-10-01 20:15 ` David S. Miller
2004-10-01 20:33 ` John Heffner
2004-10-01 23:19 ` Andi Kleen
2004-10-02 0:04 ` David S. Miller
2004-10-01 13:06 ` Herbert Xu
2004-10-03 21:50 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041001121123.19511403.ak@suse.de \
--to=ak@suse.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jheffner@psc.edu \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).