mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuel Meder <meder@mcs.anl.gov>
To: linux-kernel@vger.kernel.org
Subject: TCP capture effect (was Re: Linux TCP impotency)
Date: Mon, 14 May 2001 16:15:12 -0500	[thread overview]
Message-ID: <20010514161509.B3192@titan.mcs.anl.gov> (raw)


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



             reply	other threads:[~2001-05-14 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-14 21:15 Samuel Meder [this message]
2001-05-14 21:25 ` Alan Cox
2001-05-14 21:46 ` Andi Kleen
2001-05-15  3:49   ` TCP capture effect :: estimate queue length ? God
2001-05-15  6:06     ` Ralf Baechle
2001-05-15  7:50       ` TCP capture effect :: estimate queue length ? :: pathchar God
2001-05-15  3:54   ` TCP capture effect :: estimate queue length ? David S. Miller
2001-05-15  4:44     ` God

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=20010514161509.B3192@titan.mcs.anl.gov \
    --to=meder@mcs.anl.gov \
    --cc=linux-kernel@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®