From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Ivan Novick <novickivan@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: 200 millisecond timeouts in TCP
Date: Fri, 4 Jun 2010 02:45:28 +0200 [thread overview]
Message-ID: <20100604004528.GH6914@nuttenaction> (raw)
In-Reply-To: <AANLkTimP3IJzLUew7avKjDq7M2imLi7QHGBwyg_2zrPo@mail.gmail.com>
* Ivan Novick | 2010-06-03 17:11:07 [-0700]:
>resending tcpdump output as attachments.
Thank you, but where did you see a spurious retransmission? I looked over the
trace and didn't find any. (it is late here, so most likely I missed it ;-)
HGN
next prev parent reply other threads:[~2010-06-04 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 22:37 200 millisecond timeouts in TCP Ivan Novick
2010-06-03 22:51 ` Mitchell Erblich
2010-06-03 23:10 ` Hagen Paul Pfeifer
2010-06-04 0:05 ` Ivan Novick
2010-06-04 0:11 ` Ivan Novick
2010-06-04 0:45 ` Hagen Paul Pfeifer [this message]
2010-06-04 1:13 ` Mitchell Erblich
2010-06-04 6:58 ` Ryousei Takano
2010-06-04 15:02 ` Satoru SATOH
2010-06-04 22:55 ` Ryousei Takano
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=20100604004528.GH6914@nuttenaction \
--to=hagen@jauu.net \
--cc=netdev@vger.kernel.org \
--cc=novickivan@gmail.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).