Re: Linux TCP - unexpected retransmissions
- From: Dan N <dan@xxxxxxxxxxxxx>
- Date: 30 May 2007 01:15:29 GMT
On Tue, 29 May 2007 06:15:00 -0700, Francois wrote:
We
suspect that under certain conditions (heavy burst of messages, or
messages arriving at the same time), the stack drops or postpones
processing of events (holding locks, buffering) causing timers to
trigger retransmissions.
That sounds like a reasonable explanation to me. Or the link layer drops
data because of timing constraints and/or limited resource, so the tcp
stack never sees it.
Others have suggested using link layer protocol only, but what about using
udp?
Dan
.
- Follow-Ups:
- Re: Linux TCP - unexpected retransmissions
- From: Francois
- Re: Linux TCP - unexpected retransmissions
- References:
- Linux TCP - unexpected retransmissions
- From: Francois
- Re: Linux TCP - unexpected retransmissions
- From: Allen McIntosh
- Re: Linux TCP - unexpected retransmissions
- From: Francois
- Linux TCP - unexpected retransmissions
- Prev by Date: Re: Getting "ICMP Host redirect from gateway" response
- Next by Date: Re: IPTables configuration for SSH
- Previous by thread: Re: Linux TCP - unexpected retransmissions
- Next by thread: Re: Linux TCP - unexpected retransmissions
- Index(es):