linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: God <atm@sdk.ca>
To: "David S. Miller" <davem@redhat.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: TCP capture effect :: estimate queue length ?
Date: Tue, 15 May 2001 00:44:24 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0105150030160.23642-100000@scotch.homeip.net> (raw)
In-Reply-To: <15104.43139.354492.914572@pizda.ninka.net>

On Mon, 14 May 2001, David S. Miller wrote:

> God writes:
>  > Speaking of queues on routers/servers, does such a util exist that would
>  > measure (even a rough estimate), what level of congestion (queueing) is
>  > happening between point A and B ?
> 
> Not that I know of, but it is funny you mention this because this is
> basically the kind of calculation the TCP Vegas congestion avoidance
> scheme attempts to make.  At it's core, it is trying to estimate the
> size of router queues from local machine to remote machine based upon
> "congestion events" (packet drop, etc.).


Really? .. hmmm... might just have to go read up on it.  I have my own
ideas of how to go about doing it (pretty simple I think .. unless I'm
missing something other then coding ability .... heh). 

 My basic reason for wanting such a beast was to
convince one internet provider (who shall remain nameless), that from
at home *cough* to the gateway, was under extreame congestion.  After
finaly speaking with a tech who knew the difference between him and
a dip switch, he agreed there was a serious problem (queues
were exceeding 190/255 tx/rx, logs were showing the link upstream
from the gateway was loosing sync multiple times per hour .. etc etc).

The path to that however was long and very frustrating.  Trying to explain
that
although you can ping me fine and I can ping you fine, you still have a
serious problem; can be very confusing to some.


Thanks for the pointer :)




  reply	other threads:[~2001-05-15  4:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-14 21:15 TCP capture effect (was Re: Linux TCP impotency) Samuel Meder
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 [this message]
2001-05-15 11:33 Joerg Pommnitz

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=Pine.LNX.4.21.0105150030160.23642-100000@scotch.homeip.net \
    --to=atm@sdk.ca \
    --cc=ak@suse.de \
    --cc=davem@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).