From: Ralf Baechle <ralf@uni-koblenz.de>
To: God <atm@sdk.ca>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: TCP capture effect :: estimate queue length ?
Date: Tue, 15 May 2001 03:06:45 -0300 [thread overview]
Message-ID: <20010515030645.A15896@bacchus.dhis.org> (raw)
In-Reply-To: <20010514234604.A4694@gruyere.muc.suse.de> <Pine.LNX.4.21.0105142339470.23642-100000@scotch.homeip.net>
In-Reply-To: <Pine.LNX.4.21.0105142339470.23642-100000@scotch.homeip.net>; from atm@sdk.ca on Mon, May 14, 2001 at 11:49:16PM -0400
On Mon, May 14, 2001 at 11:49:16PM -0400, God wrote:
> > Packets are dropped when a device queue
> > fills, and when one sender is much faster than the other the faster sender
> > often wins the race, while the packets of the slower one get dropped.
>
> [.....]
>
> 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 ? I'd be curious how badly congested some
> things upstream from me are...... I know I can use ping or
> traceroute ... but they don't report queueing or bursting. Both measure
> latency and packetloss ... short of stareing at a running ping that is
> ... <G>
Pathchar, yet another Van Jacobsen toy does this. Unfortunately the old
and rotten pre-version you can find in ftp.ee.lbl.gov:/pathchar/ is afaik
the last one. In the past it served me well you find about how ISPs are
lying ... 100mbit backbone = fast ethernet in their computer room ...
Ralf
next prev parent reply other threads:[~2001-05-15 6:17 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 [this message]
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
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=20010515030645.A15896@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=ak@suse.de \
--cc=atm@sdk.ca \
--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).