Re: [tsvwg] thoughts on operational queue settings (Re: CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04)

Toerless Eckert <tte@cs.fau.de> Thu, 12 April 2018 09:12 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3E67126B72 for <tsvwg@ietfa.amsl.com>; Thu, 12 Apr 2018 02:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.95
X-Spam-Level:
X-Spam-Status: No, score=-3.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
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 JGAsBR5uYVWP for <tsvwg@ietfa.amsl.com>; Thu, 12 Apr 2018 02:12:39 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC537124F57 for <tsvwg@ietf.org>; Thu, 12 Apr 2018 02:12:39 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 4983358C4B0; Thu, 12 Apr 2018 11:12:35 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 3AC4E440214; Thu, 12 Apr 2018 11:12:35 +0200 (CEST)
Date: Thu, 12 Apr 2018 11:12:35 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, tsvwg@ietf.org
Message-ID: <20180412091235.i3dj3j4ktvriq5fq@faui48f.informatik.uni-erlangen.de>
References: <20180406160344.xwfqgzhzfto56jhq@faui48f.informatik.uni-erlangen.de> <5252b232-13df-fb19-227f-95694572b86c@kit.edu> <20180412012544.tmnzec3zddlyrmlb@faui48f.informatik.uni-erlangen.de> <39fb9195-b46f-945f-d414-936f97a59d87@gmail.com> <alpine.DEB.2.20.1804120818210.18650@uplift.swm.pp.se> <20180412080515.g5qkjqmluru26nib@faui48f.informatik.uni-erlangen.de> <alpine.DEB.2.20.1804121007560.18650@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1804121007560.18650@uplift.swm.pp.se>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Skot0xFqhWOGLqMohE8GGM6GOZM>
Subject: Re: [tsvwg] thoughts on operational queue settings (Re: CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Apr 2018 09:12:42 -0000

On Thu, Apr 12, 2018 at 10:14:00AM +0200, Mikael Abrahamsson wrote:
> On Thu, 12 Apr 2018, Toerless Eckert wrote:
> 
> > I would hope today we could get a separate WFQ for LE on all
> > platforms which looks to me like the much easier and easier to
> > predict solution. If you tell me thats not the case, my
> > interest to delve again into RED profiles will raise again *sigh*
> 
> There are too many platforms and they're all different as you already said.
> Common platforms will give you the possibility of having a few queues, so I
> will also investigate what the result would be of having three queues, one
> for LE, one for BE and one for rest, where LE gets 5% and the two other
> queues share the rest (getting half the bw each if both are congested).
> 
> This kind of setup would result in no congestion seen by rest of traffic
> even if BE and LE are fully congested.

Right. Whats "the rest" ?

Stuff like IPTV/voice/guaranteed L3VPN service traffic or the like ?

> If I set the LE drop profile to 1ms/2ms then it stopped working when there
> was BE congestion. I think this is not what one wants to happenn for normal
> customers, instead LE traffic should get some bandwidth even if it's a
> smallish single digit percentage of the total.

Argument in favour of some small > 0 share of bandwidth:

It does allows for many apps to continue in LE working without change
because they would just become just terribly slow - but would not need to
be restarted/rewritten which is necessary if the rate would go to
0 for periods longer than common TCP timeouts.

The other interesting question for the LE queue is what impact
the queue size has. If i remember correctly, the queue size
is not really in msec even if it can be specified in msec, right ?

Instead it would be a translation of msec to an actual #packet/#byte amount
for the nominal share of the queue, right ? (i am not quite sure, would
need to check docs).

I am asking, because if that interpretation is right, and queue size
of LE is e.g.: 20 msec at 5% share of the link, but LE actually
get 100% of link when BE is unused, then queue size in that sitution
would be just 1 msec, and that might have a negative impact.

Cheers
    Toerless