netdev
[Top] [All Lists]

Re: way of figuring out total number of retransmitted packets on a TCP s

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: way of figuring out total number of retransmitted packets on a TCP socket?
From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
Date: Thu, 21 Oct 2004 01:44:23 +0200
Cc: "David S. Miller" <davem@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <20041020230405.GE995@xxxxxxxxxxxxx>
References: <20041020130134.GC24757@xxxxxxxxxxxxxxxxx> <20041020151448.51209278.davem@xxxxxxxxxxxxx> <20041020223547.GJ29583@xxxxxxxxxxxxxxxxx> <20041020155352.1c9b70f6.davem@xxxxxxxxxxxxx> <20041020230405.GE995@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Thu, Oct 21, 2004 at 01:04:05AM +0200, Andi Kleen wrote:

> Is it really necessary? Our struct sock is already bloated enough 
> as is ... If Lennert needs it for some obscure purpose it's probably
> better if he just does it locally.

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.

Determining optimal routing within the internet is a somewhat of random
process, and a lot of ISPs just always use the route with the shortest
AS-path even though a lot of times that turns out not to be the best
path at all (in terms of latency/loss.)


--L

<Prev in Thread] Current Thread [Next in Thread>