Re: [aqm] thoughts on operational queue settings (Re: [tsvwg] CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04) (fwd)
Mikael Abrahamsson <swmike@swm.pp.se> Thu, 12 April 2018 11:23 UTC
Return-Path: <swmike@swm.pp.se>
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 2107C1243FE for <aqm@ietfa.amsl.com>; Thu, 12 Apr 2018 04:23:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q3E3t3kvXyQG for <aqm@ietfa.amsl.com>; Thu, 12 Apr 2018 04:23:17 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BC5E120727 for <aqm@ietf.org>; Thu, 12 Apr 2018 04:23:17 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 1299AAF; Thu, 12 Apr 2018 13:23:15 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1523532195; bh=jeb3vsArvpQfPYM24s65I46N5eFOPKaJYTpMYnzDJqk=; h=Date:From:To:Subject:In-Reply-To:References:From; b=WPtnd/H+mrK7L56jAG/nBHKtBe6bT9aUJoFW4dOG29pNJhQeH8jGegxSqpTCNpIEm uepqmKaaSt0cRj6dgmMQG9/NWIlYHer9CvJvmFBbwkLMVcRIHjuKCDDzoguOWmJFiH xNLYAMJcmZEFiauIHFxRu19Vci6zaPBeqkaBwWyQ=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 1089A9F for <aqm@ietf.org>; Thu, 12 Apr 2018 13:23:15 +0200 (CEST)
Date: Thu, 12 Apr 2018 13:23:15 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: aqm@ietf.org
In-Reply-To: <alpine.DEB.2.20.1804120839290.18650@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.20.1804121317290.18650@uplift.swm.pp.se>
References: <alpine.DEB.2.20.1804120839290.18650@uplift.swm.pp.se>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/c4bPWGCdJjLBWKZn25WJpNBLEVo>
Subject: Re: [aqm] thoughts on operational queue settings (Re: [tsvwg] CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04) (fwd)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 12 Apr 2018 11:23:20 -0000
On Thu, 12 Apr 2018, Mikael Abrahamsson wrote: > I am also going to test a 3 queue setup, where each of these groups of > DSCP values would go into different queues where LE would perhaps be > assured 5% of BW and the rest split evenly between a BE and "everything > else" queue. If I did that, I would probably not start dropping LE > traffic until 10-20ms buffer fill. I tried the following configuration which yielded expected results. Good thing here is that if you fill up BE and run some !BE (mikabr-rest class) then it basically doesn't get any added delay at all. There were no hits on class-default, I just keep it there in case there is some traffic that won't be matched by the others. I tried speeds down to 10 megabit/s, where the BE RED profile causes significant buffer delay, up to 30-40ms with 10 concurrent TCP sessions. So these values are not "one size fits all", but they're at least much better than FIFO with huge buffers and LE is well controlled compared to the other traffic. Again, I'm aiming to write up something about this for people to take to replace their overbuffered FIFOs they might have towards customers today, not produce something that is wonderfully great, but not widely supported in current hw. policy-map OUT-QOS-SERVICE-1-2011 class mikabr-BE random-detect 10 ms 1000 ms bandwidth percent 40 ! class mikabr-LE random-detect 10 ms 1000 ms bandwidth percent 5 ! class mikabr-rest random-detect 10 ms 1000 ms bandwidth percent 40 ! class class-default bandwidth percent 5 ! end-policy-map policy-map OUT-QOS-1-2011 class class-default service-policy OUT-QOS-SERVICE-1-2011 shape average 400 mbps 100 us class-map match-any mikabr-BE match dscp 0 2-7 end-class-map ! class-map match-any mikabr-LE match dscp 1 8 end-class-map ! class-map match-any mikabr-rest match dscp 9-63 end-class-map -- Mikael Abrahamsson email: swmike@swm.pp.se
- [aqm] thoughts on operational queue settings (Re:… Mikael Abrahamsson
- Re: [aqm] thoughts on operational queue settings … Jonathan Morton
- Re: [aqm] thoughts on operational queue settings … Mikael Abrahamsson
- Re: [aqm] thoughts on operational queue settings … Jonathan Morton
- Re: [aqm] thoughts on operational queue settings … Mikael Abrahamsson