Re: [aqm] AQM schemes: Queue length vs. delay based

Naeem Khademi <naeem.khademi@gmail.com> Thu, 14 November 2013 16:05 UTC

Return-Path: <naeem.khademi@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F037F21E80B2 for <aqm@ietfa.amsl.com>; Thu, 14 Nov 2013 08:05:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.305
X-Spam-Level:
X-Spam-Status: No, score=-2.305 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gxo26L-mcWuG for <aqm@ietfa.amsl.com>; Thu, 14 Nov 2013 08:05:07 -0800 (PST)
Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com [IPv6:2607:f8b0:400c:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2209D21E80D2 for <aqm@ietf.org>; Thu, 14 Nov 2013 08:05:07 -0800 (PST)
Received: by mail-vb0-f50.google.com with SMTP id x11so1866934vbb.37 for <aqm@ietf.org>; Thu, 14 Nov 2013 08:05:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hMR5IJ/Ux6Sbgfq/XXmavKItIDv0NORorPhFkC8NvJc=; b=rQGF4Xed5qEtB9T1syQF6TWh8LSihxnZcfL0glEYj+JT8hY3fqv+9ul+vpVvWPP57e Ds+AdrxwvMN42HOD6hGp1auIshyJL2H8eJUqrOGQ4Zh8sypAWuhKWJtq0uZXJRxjOdiy HT9oUOpgTxe88ofUP/44rj9FKC3hWpSSz3RaQRGCMMXK65vrhkXtvG3XzU7EZyMxr6lF Ls95X3ETcPhhmGCZVEkJcTd6Ltmlvla7pEK7uoZHIq4lTn5F6Cu1LKynj1puL78d1+vV RYc/Mt08fcOvZJ1E8buszuvtKlmJYsIA98YDh93LD0m3E6YTR1gCbOGEJL1uXiWGBMIK q+YA==
MIME-Version: 1.0
X-Received: by 10.58.151.3 with SMTP id um3mr111269veb.97.1384445104553; Thu, 14 Nov 2013 08:05:04 -0800 (PST)
Received: by 10.220.109.5 with HTTP; Thu, 14 Nov 2013 08:05:04 -0800 (PST)
In-Reply-To: <CA+-tSzyk=myS9B5tJ465C2JG9QvH8fPCG6Uu1iZ94TgPwV9s+w@mail.gmail.com>
References: <CA+-tSzyKT9gS_12V=yyia8iPt9FiDg6=NRKrB3FLdCRDTi=6Pg@mail.gmail.com> <201311132323.rADNNIKM047235@gateway1.ipv6.occnc.com> <CA+-tSzyk=myS9B5tJ465C2JG9QvH8fPCG6Uu1iZ94TgPwV9s+w@mail.gmail.com>
Date: Thu, 14 Nov 2013 17:05:04 +0100
Message-ID: <CAEjQQ5U+86aT=V9FxvSam9mQNzvUdtuf25HV55XXMQPE5095Og@mail.gmail.com>
From: Naeem Khademi <naeem.khademi@gmail.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>
Content-Type: multipart/alternative; boundary="047d7b6d7b26ab050604eb253ebf"
Cc: Preethi Natarajan <preethi.cis@gmail.com>, "aqm@ietf.org" <aqm@ietf.org>, Michael Welzl <michawe@ifi.uio.no>, curtis@ipv6.occnc.com
Subject: Re: [aqm] AQM schemes: Queue length vs. delay based
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Nov 2013 16:05:08 -0000

On Thu, Nov 14, 2013 at 12:33 AM, Anoop Ghanwani <anoop@alumni.duke.edu>wrote:

>
>
>
> On Wed, Nov 13, 2013 at 3:23 PM, Curtis Villamizar <curtis@ipv6.occnc.com>wrote:
>
>>
>> Including unrealistic scenarios, like going from near zero traffic to 10
>> interfaces feeding one at full speed until overflow occurs, is
>> counterproductive.
>
>
> It is actually a problem that keeps many people busy because a number of
> data center switches have very high port count with very small buffers.
>  Some people address these buy using switches with bigger buffers, but
> that's not a luxury that everyone indulges in.
>

Fair point about the incast problem and I personally think AQMs designed
for data centers should address that.


> That is why I specifically asked the question at the AQM meeting about
> applicability of AQM to all types of networks/switches.  I was told the
> answer is "yes" and so I would like to see this scenario addressed as well.
>
>

Below is my personal opinion, but hopefully Fred can clarify this better
based on the AQM recommendations draft:

"applicability of AQM to all types of networks/switches" => "yes"

"applicability of *any* AQM to all types of networks/switches" => "no"


> Perhaps AQM cannot help this, but hopefully it won't hurt.  Trying to do
> fancy things with small buffers is challenging.
>

AQM will most likely to help from data centers to the access links, and so
on. But we may possibly need different AQMs for different network
scenarios; The fact that an AQMs should be auto-tunable doesn't imply that
it can be applied everywhere and we may need different auto-tunable AQMs
specifically designed for different networks (ideally better if we could
use fewer of them and they could work everywhere). I hope I'm not wrong.


>
> Anoop
>

Naeem