[tsvwg] FQ-CoDel response to unresponsive traffic (was: Related to "Non-L4S traffic abusing the L-queue" discussion during the interim)

Bob Briscoe <ietf@bobbriscoe.net> Sat, 26 February 2022 13:45 UTC

Return-Path: <ietf@bobbriscoe.net>
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 EE18E3A143D for <tsvwg@ietfa.amsl.com>; Sat, 26 Feb 2022 05:45:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 uMkBkFPqBPjD for <tsvwg@ietfa.amsl.com>; Sat, 26 Feb 2022 05:45:32 -0800 (PST)
Received: from mail-ssdrsserver2.hostinginterface.eu (mail-ssdrsserver2.hostinginterface.eu [185.185.85.90]) (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 DEDDE3A1441 for <tsvwg@ietf.org>; Sat, 26 Feb 2022 05:45:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=MYDKYqRg057HlgyctxmgOTZXNMxTKw1GehfFvRExhK8=; b=EExKcGUDIPOHuAFm8vljKNWLRG 1FaQPCkwtJcBWBE3fcigKSqPjYD+VHll9aFBk9M8e0GKKPlF56Dd94yeOk4STLtvmtcbKNaBU8m5a 2LgZyhy6DIOmLKPEEo21HtioFoYEjwCE+72yqSXQBbn0rLz2vfDpgjySpYiqsfzwYq1MHo0eD2whS OEh2b3torO5zewzvQ5X/9+TeVzKKZO8FhrYsznbnuMsxhEyohjOhX15GzltG4/A9InCwAd2TeNuUG T+UL+oWcnWUzt/plDGtF5T7OOant2WnM4DlbrCLqSNIKFIo+wEAHavM4qWO2YXYs0cYERV3YKCg/i e1V7302g==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:55644 helo=[192.168.1.11]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <ietf@bobbriscoe.net>) id 1nNxOD-0006em-Gu; Sat, 26 Feb 2022 13:45:26 +0000
Message-ID: <5114db28-89ac-1eae-b846-22ae37391c6c@bobbriscoe.net>
Date: Sat, 26 Feb 2022 13:45:24 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-GB
To: Dave Taht <dave.taht@gmail.com>, "De Schepper, Koen (Nokia - BE/Antwerp)" <koen.de_schepper@nokia-bell-labs.com>
Cc: tsvwg IETF list <tsvwg@ietf.org>
References: <AM9PR07MB7313D5AAF6B9D66C74CC35A1B9369@AM9PR07MB7313.eurprd07.prod.outlook.com> <AM9PR07MB7313F1401B14F6F2DB72A2B2B93E9@AM9PR07MB7313.eurprd07.prod.outlook.com> <MN2PR19MB40454F60DEE5735EAD428465833E9@MN2PR19MB4045.namprd19.prod.outlook.com> <CADVnQyk+uSX9GJtMBnsBhn9NzY+L3BKfhhUJ=yu4Aya98YEonw@mail.gmail.com> <MN2PR19MB40458624D266CDB54009AB19833E9@MN2PR19MB4045.namprd19.prod.outlook.com> <AM9PR07MB731311A9E4532FD501B5D94CB93E9@AM9PR07MB7313.eurprd07.prod.outlook.com> <CAA93jw4=JuO9UqBoHLHXCQrLn7toTqPDerFehDajEH2-2dtZWA@mail.gmail.com> <CAA93jw4CtiYjBg9RAFuOjJHX4T7aUQ07KdetWSgKrNgJg=DPPA@mail.gmail.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
In-Reply-To: <CAA93jw4CtiYjBg9RAFuOjJHX4T7aUQ07KdetWSgKrNgJg=DPPA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hostinginterface.eu
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: ssdrsserver2.hostinginterface.eu: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hostinginterface.eu: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/SGCiix4BGR8z_D8-gtG4JmSZZXM>
Subject: [tsvwg] FQ-CoDel response to unresponsive traffic (was: Related to "Non-L4S traffic abusing the L-queue" discussion during the interim)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 26 Feb 2022 13:45:37 -0000

Dave,

I will keep reminding everyone that this shift of topic to FQ-CoDel is 
distracting from the task at hand:
     "Is Jonathan going to confirm that his 'throughput bonus' and 'fast 
lane' accusations against DualQ are baseless because his experiment was 
broken?"

Nonetheless, response on FQ-CoDel is below, tagged [BB]...

On 25/02/2022 21:06, Dave Taht wrote:
> while I do not want to spend much time nitpicking this document...
>
> "causing most of the time tail-drop" stood out. codel, fq_codel, cake
> all do head drop, and always have.

[BB] For the list, we're talking about Figure 5 here: 
https://l4steam.github.io/overload-results/

I'm nearly certain that the cap at 600 ms is tail drop.
Cause: The control law increases head drop so slowly that the flow-queue 
containing the unresponsive flow eventually fills the buffer allocated 
to the whole qdisc. Then I believe it moves into what Jonathan calls 
'tallest sunflower' drop mode (tail drop focused on the longest flow-queue).

To help prove this, here's an experiment Asad ran for me last Oct on 
FQ-CoDel with an unresponsive flow rate just greater than the link rate.
https://bobbriscoe.net/projects/latency/CoDel-delta-bug.pdf#page=4
We were testing very slight overload, so it would stay in head drop 
mode, without hitting the need for tail drop. The plot shows a similar 
series of humps in the queue, but without the cut-off due to tail drop. 
So it's fairly conclusive that Koen's Fig 5 is showing tail drop.

I'll answer your question (on the SANE list) about why the humps repeat, 
but that's a trivial bug compared to the time CoDel takes in the first 
place.
It's a design flaw, not a bug.
The so-called 'control' law never even measures the queue it is meant to 
be controlling.
Here's some history:

* On 12-Nov-2013 I reported that to Kathie and Van as CoDel designers, 
cc the AQM list:
https://mailarchive.ietf.org/arch/msg/aqm/l4H1QdRl8B-E5FWpJh4w50B_nQE/
* No response by anyone for over 18 months, until...
* 07-Jun-2015: Toke confirmed my analysis empirically (see it, via same 
thread above)
    Toke's plot: 
https://kau.toke.dk/ietf/codel-drop-rate/codel-drop-rate.svg
* On 30-Sep-2015 you (DaveT) said "cake uses a better curve for CoDel 
but we still need to do more testing in the lab"
    As far as I understand it, that missed the point: CAKE's curve is 
still extremely slow, but somewhat faster than CoDel.
    But, CAKE's control law still never measures the queue it is meant 
to be controlling.
* 25-Feb-2022: You say you don't want to spend much time nitpicking 
Koen's experiment.
     If not you, someone needs to grasp this nettle, given FQ-CoDel is 
the default qdisc in the Linux mainline.



Bob

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/