From: Wenji Wu <wenji@fnal.gov>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: 'Netdev' <netdev@vger.kernel.org>
Subject: Re: RE: A Linux TCP SACK Question
Date: Mon, 14 Apr 2008 17:07:21 -0500 [thread overview]
Message-ID: <fbbd26f52a58.48038f49@fnal.gov> (raw)
In-Reply-To: <Pine.LNX.4.64.0804141927060.28474@wrl-59.cs.helsinki.fi>
> Hmm, now there are even less retransmissions (barely some with
> the SACK in the end).
>
> I suppose the reordering detection is good enough to kill them. ...You
>
> could perhaps figure that out from MIBs if you would want to.
>
Yes, the web100 shows that the tcp_reordering could be as large as 127.
I just rerun the following experimetns to show why there are few retransmissions in my previous posts.
(1) Flush the sytem routing cache by running "ip route flush cache" before running and tcpdumping the traffic
(2) Before running and tcpdumping the traffic, run a data transmission test to generate tcp_reordering in the routing cache.
Do not flush the routing cache. Then running and tcpdumping the traffic.
Both experiments with sack off.
The results is posted to
https://plone3.fnal.gov/P0/WAN/Members/wenji/adaptive_tcp_reordering/
So, the few retransmissions in my previous post are really caused by the routing cache.
But flushing cahce has nothing to do with SACK on/off. Still the trhoughput with SACK off is better than that of with SACK on.
wenji
next prev parent reply other threads:[~2008-04-14 22:14 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 4:54 A Linux TCP SACK Question Wenji Wu
2008-04-04 16:27 ` John Heffner
2008-04-04 17:49 ` Wenji Wu
2008-04-04 18:07 ` John Heffner
2008-04-04 20:00 ` Ilpo Järvinen
2008-04-04 20:07 ` Wenji Wu
2008-04-04 21:15 ` Wenji Wu
2008-04-04 21:33 ` Ilpo Järvinen
2008-04-04 21:39 ` Ilpo Järvinen
2008-04-04 22:14 ` Wenji Wu
2008-04-05 17:42 ` Ilpo Järvinen
2008-04-05 21:17 ` Sangtae Ha
2008-04-06 20:27 ` Wenji Wu
2008-04-06 22:43 ` Sangtae Ha
2008-04-07 14:56 ` Wenji Wu
2008-04-08 6:36 ` Ilpo Järvinen
2008-04-08 12:33 ` Wenji Wu
2008-04-08 13:45 ` Ilpo Järvinen
2008-04-08 14:30 ` Wenji Wu
2008-04-08 14:59 ` Ilpo Järvinen
2008-04-08 15:27 ` Wenji Wu
2008-04-08 17:26 ` Ilpo Järvinen
2008-04-14 22:47 ` Wenji Wu
2008-04-15 0:48 ` John Heffner
2008-04-15 8:25 ` Ilpo Järvinen
2008-04-15 18:01 ` Wenji Wu
2008-04-15 22:40 ` John Heffner
2008-04-16 8:27 ` David Miller
2008-04-16 9:21 ` Ilpo Järvinen
2008-04-16 9:35 ` David Miller
2008-04-16 14:50 ` Wenji Wu
2008-04-18 6:52 ` David Miller
2008-08-27 14:38 ` about Linux adaptivly adjusting ssthresh Wenji Wu
2008-08-27 22:48 ` John Heffner
2008-08-28 0:53 ` Wenji Wu
2008-08-28 6:34 ` Ilpo Järvinen
2008-08-28 14:20 ` about Linux adaptivly adjusting dupthresh Wenji Wu
2008-08-28 18:53 ` Ilpo Järvinen
2008-08-28 19:30 ` Wenji Wu
2008-04-16 14:40 ` A Linux TCP SACK Question John Heffner
2008-04-16 15:03 ` Ilpo Järvinen
2008-04-16 14:46 ` Wenji Wu
2008-04-15 15:45 ` Wenji Wu
2008-04-15 16:39 ` Wenji Wu
2008-04-15 17:01 ` John Heffner
2008-04-15 17:08 ` Ilpo Järvinen
2008-04-15 17:23 ` John Heffner
2008-04-15 18:00 ` Matt Mathis
2008-04-15 17:55 ` Wenji Wu
2008-04-08 15:57 ` John Heffner
2008-04-08 14:07 ` John Heffner
2008-04-14 16:10 ` Wenji Wu
2008-04-14 16:48 ` Ilpo Järvinen
2008-04-14 22:07 ` Wenji Wu [this message]
2008-04-15 8:23 ` Ilpo Järvinen
2008-04-04 21:40 ` Wenji Wu
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=fbbd26f52a58.48038f49@fnal.gov \
--to=wenji@fnal.gov \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
/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).