From: "David S. Miller" <davem@davemloft.net>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: ak@suse.de, netdev@oss.sgi.com
Subject: Re: way of figuring out total number of retransmitted packets on a TCP socket?
Date: Wed, 20 Oct 2004 16:44:51 -0700 [thread overview]
Message-ID: <20041020164451.7746b595.davem@davemloft.net> (raw)
In-Reply-To: <20041020234423.GB31265@xi.wantstofly.org>
On Thu, 21 Oct 2004 01:44:23 +0200
Lennert Buytenhek <buytenh@wantstofly.org> wrote:
> My application is a large-ish streaming video and file download service,
> where I want to be able to automatically report on netblocks that are
> seeing unusual packet loss, and then use that data to alert our NOC
> and subsequently kick my transit providers with.
Isn't this what RSVP is for? I realize that you may not be in
a position to use RSVP end-to-end as necessary, but watching for
retransmits by hand seems like simply a hackish way to do RSVP.
Furthermore, non-timeout based retransmits are actually normal even
on local subnets when a gigabit switch drops a packet to prevent
internal deadlocks and stuff like that. I've seen this quite a bit.
next prev parent reply other threads:[~2004-10-20 23:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 13:01 way of figuring out total number of retransmitted packets on a TCP socket? Lennert Buytenhek
2004-10-20 13:25 ` Baruch Even
2004-10-20 22:16 ` David S. Miller
2004-10-20 22:14 ` David S. Miller
2004-10-20 22:35 ` Lennert Buytenhek
2004-10-20 22:53 ` David S. Miller
2004-10-20 23:04 ` Andi Kleen
2004-10-20 23:07 ` David S. Miller
2004-10-20 23:27 ` Andi Kleen
2004-10-20 23:42 ` David S. Miller
2004-10-21 1:18 ` Arnaldo Carvalho de Melo
2004-10-20 23:44 ` Lennert Buytenhek
2004-10-20 23:44 ` David S. Miller [this message]
2004-10-21 9:01 ` Lennert Buytenhek
2004-10-21 4:37 ` David S. Miller
2004-10-26 13:47 ` Lennert Buytenhek
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=20041020164451.7746b595.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.de \
--cc=buytenh@wantstofly.org \
--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).