Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM for RTT

Bob Briscoe <bob.briscoe@bt.com> Tue, 12 November 2013 23:03 UTC

Return-Path: <bob.briscoe@bt.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 652F211E8102; Tue, 12 Nov 2013 15:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.742
X-Spam-Level:
X-Spam-Status: No, score=-2.742 tagged_above=-999 required=5 tests=[AWL=-0.370, BAYES_00=-2.599, 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 EquY7NDhynvd; Tue, 12 Nov 2013 15:03:43 -0800 (PST)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.98]) by ietfa.amsl.com (Postfix) with ESMTP id 8146F21E80A5; Tue, 12 Nov 2013 15:03:32 -0800 (PST)
Received: from EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) by EVMHR66-UKRD.bt.com (10.187.101.21) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 12 Nov 2013 23:03:30 +0000
Received: from EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) by EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) with Microsoft SMTP Server (TLS) id 8.3.297.1; Tue, 12 Nov 2013 23:03:27 +0000
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) with Microsoft SMTP Server id 14.2.347.0; Tue, 12 Nov 2013 23:03:22 +0000
Received: from BTP075694.jungle.bt.co.uk ([10.215.131.145]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id rACN3LUX003607; Tue, 12 Nov 2013 23:03:21 GMT
Message-ID: <201311122303.rACN3LUX003607@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 12 Nov 2013 23:03:20 +0000
To: "Scheffenegger, Richard" <rs@netapp.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <012C3117EDDB3C4781FD802A8C27DD4F25E8908F@SACEXCMBX02-PRD.h q.netapp.com>
References: <201311111618.rABGILbC031136@bagheera.jungle.bt.co.uk> <CEA65B19.21ED5%g.white@cablelabs.com> <012C3117EDDB3C4781FD802A8C27DD4F25E8908F@SACEXCMBX02-PRD.hq.netapp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Cc: Greg White <g.white@CableLabs.com>, tsv-area IETF list <tsv-area@ietf.org>, AQM IETF list <aqm@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [aqm] [tsvwg] Immediate ECN: Autotuning AQM for RTT
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: Tue, 12 Nov 2013 23:03:48 -0000

Richard,

I've replied separately to Greg - apologies for splitting the thread. Inline...

At 13:18 12/11/2013, Scheffenegger, Richard wrote:
>Hi Greg et.al.,
>
>(chair hat off)
>
> > I don't have a lot of confidence that I can recommend something to be
> > burned into silicon at this point (and doing it in software is a non-
> > starter).  The "turned on or off by operators later" would be a given, but
> > if implemented based on what we know now, I don't have a lot of confidence
> > that the switch would be ever set to the "turned on" state.  I can't
> > recommend that vendors add gates for a feature that my intuition tells me
> > would never be used.  If separately configurable means something that
> > would increase the probability of the feature being used, then that's
> > great, but what specifically are we talking about?  It could be a lot of
> > gates.
>
>So, as I am not a HW guy, how many gates does one need for (W)RED, PIE, CoDel?
>
>Apparently, as state needs to be kept separately 
>for ECN and non-ECN flows, additional memory 
>plus some way of switching between which memory 
>is used for what packet is necessary; however, 
>the hardcoded algos should be the same (as far 
>as some tuneables are stored in memory instead of hardwired gates).

I'll let the hw people answer that, but it seems a reasonable point.


> > Also, you've suggested *not* differentiating between "classic ECN" and
> > "immediate ECN" in the ECT flags, but this is just a suggestion at this
> > point.  Again, not something I feel confident about taking for granted.
> > We'll continue to track this discussion though.
>
>As Bob pointed out in another email, classic ECN 
>will react to any number of marks within one RTT 
>(of that particular flow) with only a single 
>halving of the congestion window. Most other 
>transports that have been modeled after TCP/ECN 
>will behave similarly. Immediate ECN will react 
>to each mark to a smaller extent, and only a 
>full window (RTT) of marks will reduce the 
>window by half. Thus immediate ECN would be much 
>more aggressive when used with traditional RED, 
>ie. push the AQM to higher marking probabilities.

The paper (available on request, because still 
under submission) records experiments that show 
we can get equal rates between otherwise 
equivalent ECN and drop flows as long as the 
parameters of the two ramps are connected by a 
formula. This formula was found by fitting to the 
very clear curve visible along the ridge of the 
3-D plot on our slide 11 
<http://www.ietf.org/proceedings/88/slides/slides-88-tsvwg-20.pdf>.

I'm sure this will not be the whole story, but 
it's a good start. I believe that such parameter 
settings only lead to equal rates between an ECN 
and a drop flow for one of each type of flow. I 
won't be particularly worried if the relative 
rates stray from precise equality under different 
conditions, as long as there is no starvation, 
and they remain in the same ball-park.


>One venue that presents itself here, of course, 
>is to use 2nd order effect - i.e. the exact 
>marking pattern - to achive reasonable fairness 
>between transports making use of immediate and 
>classic reactions. However, I can not say 
>offhand, if this would be a practical method 
>(may require too much state in the 
>scheduling/aqm, including fine grained flow separation).

Hopefully we won't need to go there.


> > However, it seemed to me that what you were proposing was to move the
> > intelligence to the transport, and keep the queue simple. In that regard,
> > would a very simple threshold:  always mark when instantaneous queue
> > exceeds the threshold, never mark when it doesn¹t, be an acceptable way to
> > do things?
> >
> > This would be easily implementable, and could be straightforwardly
> > combined (I think) with any AQM that is controlling drops (including
> > CoDel).
>
>That is what DCTCP currently does.

I wasn't aware that DCTCP was already being used 
alongside non-ECN traffic. Is this what you meant?

>However, a simple step function is incompatible with classic ECN.

I think you mean classic ECN TCP flows. If so, I 
wouldn't state this quite so strongly (yet). I 
suspect there will be conditions where a classic 
ECN TCP will be somewhat disadvantaged. However, we need experiments to see:
* whether the disadvantage is slight,
* how many classic ECN hosts might be affected,
* and the likelihood that their owners would 
rapidly upgrade them (AFAIK, their owners must 
have already intervened manually for ECN hosts to 
already be in the wild, given I believe ECN is 
turned off by default in TCP clients under the major operating systems).


>While reading Bob's earlier comment on classic 
>vs immediate ECN, I thought that probably an 
>exponential increase in marking probability, 
>above a specific threshold (lower than drop) 
>could "autotune" to a reasonable marking rate, 
>without necessarily locking classic out when 
>immediate is used. If the linear/step function 
>employed with RED (and shown on Bobs slides) is 
>a good enough approximation needs to be 
>verified. However, the details will probably 
>also depend on the mixure of number of classic 
>vs. immediate ECN flows at the bottleneck, and their respective RTTs...

Agreed.


>Finally, as the gateways (switches) cannot rely 
>on ECN to work (either on the required 
>timescales, as the RTT is too large for small 
>buffers, or the transport/sender is not 
>reacting), even ECN traffic has to be exposed to drops

Agreed

>  - and ideally here not to the tail-drop variant.

It may not be necessary to switch an ECN flow to 
AQM-generated drops - it may be sufficient to 
switch both ECN and drop traffic to tail drop at 
the same time - when load exceeds the operating 
region of the AQM as a whole. But, you may be right - needs more experiments.


Bob



>Richard Scheffenegger
>
>
>_______________________________________________
>aqm mailing list
>aqm@ietf.org
>https://www.ietf.org/mailman/listinfo/aqm

________________________________________________________________
Bob Briscoe,                                                  BT