From: Rick Jones <rick.jones2@hp.com>
To: Felix von Leitner <felix-linuxkernel@fefe.de>
Cc: Chuck Ebbert <cebbert@redhat.com>,
linux-kernel@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: bizarre network timing problem
Date: Wed, 17 Oct 2007 15:16:31 -0700 [thread overview]
Message-ID: <471689BF.2040909@hp.com> (raw)
In-Reply-To: <20071017220019.GA22765@codeblau.de>
the packet trace was a bit too cooked perhaps, but there were indications that
at times the TCP window was going to zero - perhaps something with window
updates or persist timers?
rick jones
next prev parent reply other threads:[~2007-10-17 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071017205127.GA21334@codeblau.de>
2007-10-17 21:17 ` bizarre network timing problem Chuck Ebbert
2007-10-17 22:00 ` Felix von Leitner
2007-10-17 22:16 ` Rick Jones [this message]
2007-10-18 9:42 ` Felix von Leitner
2007-10-18 17:22 ` Rick Jones
2007-11-02 22:11 ` Felix von Leitner
2007-11-02 22:33 ` Rick Jones
2007-11-02 22:38 ` Felix von Leitner
2007-11-02 22:58 ` Rick Jones
2007-11-02 23:23 ` Felix von Leitner
2007-11-06 21:12 ` Rick Jones
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=471689BF.2040909@hp.com \
--to=rick.jones2@hp.com \
--cc=cebbert@redhat.com \
--cc=felix-linuxkernel@fefe.de \
--cc=linux-kernel@vger.kernel.org \
--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).