Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Fred Baker <fred@cisco.com>
To: Justin McCann <jneilm@gmail.com>
Cc: bloat <bloat-devel@lists.bufferbloat.net>
Subject: Re: Getting current interface queue sizes
Date: Sun, 6 Mar 2011 23:21:06 -0800	[thread overview]
Message-ID: <24D67DE4-5637-4FFE-A375-23CF52A6BBAF@cisco.com> (raw)
In-Reply-To: <AANLkTimmJ1LZfee81Sww3426gpNU2jVPZ6U+TwjQMRWo@mail.gmail.com>


On Mar 6, 2011, at 2:31 PM, Justin McCann wrote:

> Thanks for your response. This is more research-related, trying to detect what parts of the stack on an end host are exhibiting and/or causing network stalls a few RTTs or more in duration. I'm also watching the number of bytes and packets sent/received, and when activity stops altogether, looking at the queue sizes shows where things are getting held up. I don't think the approach would be as useful for a middlebox that is just doing best-effort forwarding, but it would probably work if the box was acting as a TCP proxy. So, it's not bufferbloat-related per se, but I figure having the information doesn't hurt, as long as it's not misused like you mention.

No doubt. But I think you'll find that Cisco equipment tells you the maximum queue depth, not the current queue depth, or doesn't implement the object.

  reply	other threads:[~2011-03-07 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 22:26 Justin McCann
2011-03-01  0:29 ` Fred Baker
2011-03-06 22:31   ` Justin McCann
2011-03-07  7:21     ` Fred Baker [this message]
2011-03-07 18:28       ` Jim Gettys
2011-03-07 21:18         ` Justin McCann

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=24D67DE4-5637-4FFE-A375-23CF52A6BBAF@cisco.com \
    --to=fred@cisco.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=jneilm@gmail.com \
    /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