Messages in this thread | | | Date | Mon, 14 May 2001 16:15:12 -0500 | Subject | TCP capture effect (was Re: Linux TCP impotency) | From | Samuel Meder <> |
| |
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?
Thanks
/Sam Meder
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |