From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-11-ewr.dyndns.com (mxout-103-ewr.mailhop.org [216.146.33.103]) by lists.bufferbloat.net (Postfix) with ESMTP id D2C432E0330 for ; Mon, 7 Mar 2011 09:57:57 -0800 (PST) Received: from scan-11-ewr.mailhop.org (scan-11-ewr.local [10.0.141.229]) by mail-11-ewr.dyndns.com (Postfix) with ESMTP id 8E53392D80B for ; Mon, 7 Mar 2011 07:21:08 +0000 (UTC) X-Spam-Score: -8.0 (--------) X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 171.68.10.87 Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by mail-11-ewr.dyndns.com (Postfix) with ESMTP id 1732B92D2C0 for ; Mon, 7 Mar 2011 07:21:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=911; q=dns/txt; s=iport; t=1299482468; x=1300692068; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Ork/7Qb6FRRbK5GiEkI1A9fQGMpwrTbpz56JfGwbicY=; b=iOExS5bCb7kZZ0g6iU8Csv1rTWnLV9RKYQRmAJ1659dCQRQCFGt5UpUA qj5pHhXmFsGuUVuYniKEYN4siLFXaWnPvxRfmexgJNNGzJjOhzvNE2KwL T4u6Z13ur5HZaB9OIw3YqCqfK14J8obevw42RGvzVbFZBZMwunQu3m2n/ o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEACsWdE2rR7Ht/2dsb2JhbACmSXSibJsMhWIEhRyHFA X-IronPort-AV: E=Sophos;i="4.62,276,1297036800"; d="scan'208";a="340976539" Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 07 Mar 2011 07:21:07 +0000 Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p277L6Bw008437; Mon, 7 Mar 2011 07:21:07 GMT Subject: Re: Getting current interface queue sizes Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Fred Baker In-Reply-To: Date: Sun, 6 Mar 2011 23:21:06 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <24D67DE4-5637-4FFE-A375-23CF52A6BBAF@cisco.com> References: <7A1666CF-3E98-4668-A265-F89B50D23909@cisco.com> To: Justin McCann X-Mailer: Apple Mail (2.1082) Cc: bloat X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2011 17:57:58 -0000 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.=