From: Jarek Poplawski <jarkao2@gmail.com>
To: Kristian Evensen <kristian.evensen@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Strange TCP behavior over HSDPA
Date: Tue, 29 Dec 2009 12:16:24 +0000 [thread overview]
Message-ID: <20091229121624.GC7209@ff.dom.local> (raw)
In-Reply-To: <20091229105748.GB7209@ff.dom.local>
On Tue, Dec 29, 2009 at 10:57:48AM +0000, Jarek Poplawski wrote:
> Did you try to turn off TCP window scaling btw? Anyway, under the
> tunnel ([2]), when SACK worked, it saved you a lot of retransmits.
Hmm... Actually, after re-checking, there weren't much more of those
retransmits at all. In [1] there was one more packet lost, so it took
a bit longer. In [2] (with SACK) the retransmit started earlier and
the rcv window was unchanged. So, it rather looks like differences
in timing of TCP recovery techniques.
Jarek P.
next prev parent reply other threads:[~2009-12-29 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 12:56 Strange TCP behavior over HSDPA Kristian Evensen
2009-12-29 8:30 ` Jarek Poplawski
2009-12-29 9:59 ` Kristian Evensen
2009-12-29 10:57 ` Jarek Poplawski
2009-12-29 12:16 ` Jarek Poplawski [this message]
2009-12-29 13:36 ` Jarek Poplawski
2009-12-29 14:30 ` Kristian Evensen
2009-12-29 18:31 ` Jarek Poplawski
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=20091229121624.GC7209@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=kristian.evensen@gmail.com \
--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).