[lkml]   [2001]   [May]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectTCP capture effect (was Re: Linux TCP impotency)

Alan Cox wrote:

> > causes the earlier started one to survive and the later to
> > starve. Running bcp instead of the second (which uses UDP) at
> > 11000 bytes per second caused the utilization in both directions
> > to go up nearly to 100%.
> >
> > Is this a normal TCP stack behaviour?
> Yes. TCP is not fair. Look up 'capture effect' if you want to know more.

I'm seeing a similar effect myself. When I use all my available sdsl
bandwidth (say doing a bulk data transfer), DNS lookups will often
time out. This is with the default buffer settings/2.4.4.
I'm curious about this effect so I've been trying to find information
on this and while I can find lots of information on the Ethernet
capture effect there doesn't seem to be anything on the TCP capture
effect. Could someone point me at an explanation of this effect?


/Sam Meder

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:53    [W:0.081 / U:3.760 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site