From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 231C53B29E for ; Thu, 31 Aug 2023 03:06:03 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1693465561; x=1694070361; i=moeller0@gmx.de; bh=10rNSmyAVlqDs0YtfgYYGQNKRfEd5/8zUa2LbjI8JKc=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=Hl419QY+F7Cs3CVW3Y138G4h6jvqTTsf8evRhm049OZyeKR0HRfvKuMuicZwLPNEUPL2okn wyX2uGwCiKyMM5o5UkkJ0DtN009+YRHTolR63PY9pGWuILTPkRAL0BizYCa/K6jcwGqZdDBe7 VsMrRkiulUU6NS2/Rm69hUHPS7EI+D4MWefy13LFNI1yf8XC2YfBxvwlRJwa20wCvKedr6n2v DLrJ74t8fA2MUyOESKyZy1MCO37qVrOYhNIw9oeKnUSAtMYhuQM1vPBrNpxj6DMzdrpbn9edN xLsCIfVclLXOdWretJsKrzzyE6OFSvwIczCDuxt3u+JrYos5BiHg== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from smtpclient.apple ([134.76.241.253]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MLiCo-1qK4rp1ZFQ-00HjMF; Thu, 31 Aug 2023 09:06:01 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) From: Sebastian Moeller In-Reply-To: Date: Thu, 31 Aug 2023 09:06:00 +0200 Cc: Cake List Content-Transfer-Encoding: quoted-printable Message-Id: <183E1F7D-5842-46F9-BD22-C9DD62105715@gmx.de> References: To: =?utf-8?Q?Dave_T=C3=A4ht?= X-Mailer: Apple Mail (2.3696.120.41.1.4) X-Provags-ID: V03:K1:jZp7Qjv/UPLdvWsxVtf3WOhWufHITcNECPxrjiF+TmcThpGbnYK XnuU4v/zLtkWfT873aztRp6h006RccYS3yK6aXieP3le2Z3VFfstPaZMDjipKZPALpafogS 6LLFXWVF2/WSOW31mGmmN3rwWbRTEW1rQxsUQ0aiKzzBSnFjnCSqfjglqRxBbjAR3eWloLg X9xCrIfrbWH5cdpf+ajnw== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:7A4p3jIKz30=;0YYwIiDFY7z6Ra3apXGAsvmtyk7 SL7/dGmK79PHADJG/BFL7RcVOKi72E/MVXPqhkjM8N3wwiQYwznSzQeaKwmGSLvp66c/crgNY z9yZeCGw4yZx98PuRg+qWW0PxiVJ9G2Qa3rRg8HoyUXb1vnLzQGGXQdS7mlzzcv6MknUInyZb i1i+jj+uv1dAijdBv+reTmpCpf+DqAyXun0OmTa+M4nfECLmSu86IQmPNTMn5OlJrWqPqoD1F YLa+lAbxx4oIFhxGGhV3572zvdd9GhtQAG5cRx8xo5mnw62LE5lI/EUlHl2wEKanenb0yY8ut tfwjfZqI+9jQLDL80tnHPw5w7M4zJflKP+lHKdZIac2wYw6QEQuZmzdD/Oz1hZbpsdg2DU7DI 4fLRSwZ07MVEKryLZM7eMNNCrRGDXZACeAsavJ84BqQfvv1qvIszeXRG7ZM0bP6ZHiQpSpo01 x2wpLEJeqBUY/JjaY/Slh/4mVb1XQF+M6Wpzu7kpOvLeu3L5yE0InNskBfQTa6ZsK5gMlXnx3 zr9D7erouqdkYQcZtSwmPSmvwFIV3E3gpns4GtYyiYzOYToMQCLyQiLztgDfvI9aCZ6zuyk1K 0rT90lOxcrT1N6zNc+Bnx15DMwKmX7z3HWPFqEugtxF9zGeao37gyDMEIdJm5mavGclTFZUzD eaWxOU6MiSr9oX7/AoEFzfI6KZ68KIacx833horsLrGosP42/Zw0NrmW6omU/C5ddyFuD1I8M tfbaUhzEQKmnmsfRDl4JsksggpJ/wLz5C2jelegBerxaAX8QzCqTRZvWzkW7C7EuiUZiK9X/v s8BmQsZWdhC2Ltawg8E5QpdYPgGb40RccAr2y2Ux/JOC35Q0JsoPmt2Lh+KI9TkHB6qQXE0yC ToHOteX+7ZU87RurWvQN4dM/hKvcOyXo4B3gM8cCLXWBEiwZs1/JvI3HyHpSmnAdORah5vdCg CIXgE4x6P/gELU6YcPfEcDh4pRg= Subject: Re: [Cake] Some more cakemq thoughts X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2023 07:06:04 -0000 Hi Dave, > On Aug 31, 2023, at 04:49, Dave Taht via Cake = wrote: >=20 > From: = https://docs.google.com/document/d/1tTYBPeaRdCO9AGTGQCpoiuLORQzN_bG3TAkEol= JPh28/edit#heading=3Dh.s3q8pyu1s825 >=20 > ... >=20 > The kernel has over 2500 places where it can drop packets, many of > which have been instrumented with the =E2=80=9CDrop_reason=E2=80=9D = facility. No > qdisc has drop_reason encoded into it yet. (Suggested names: > DROP_REASON_{CONGEST, OVERFLOW, FLOOD, SPIKE}). >=20 > QOS-MAP mirroring the same syntax as the wifi interface, this > establishes a direct correspondence between cake =E2=80=9Ctins=E2=80=9D = and the > settings for the linux wifi qos-map facility. [SM] Not a big fan of the qos_map syntax, but I agree that being = able to configure the cake DSCP-2-tin mapping from tc seems worthwhile, = and not reinventing the wheel with a new way to request that mapping has = merits as well (plus one could use the same string for both cake and = WiFI), so +1. > VLAN-MAP This maps from vlans to tins [SM] This will IMHO require to switch cake from soft = tin-enforcement to strict tin capacity share enforcement (at least under = competition) as otherwise the expected priorities are not delivered any = more. But I might misunderstand how cake deals with tin's exceeding = their share. For normal operation just telling users, do not put greedy = traffic into anything > BE seems OK, but for VLANs that will not really = fly IMHO. > NOWASHNQB - cake defaults to nowash allowing the passage of all dscps, > the addition of the NOWASHNQB state means it will wash out everything > except NQB. [SM] This assumes that NQB will actually work over the existing = internet reliably enough to make people switch away from say EF or VA. I = think this is wishful thinking (backed in the case of the NQB by = underwhelming engineering, and externalization of costs), that said such = a feature seems rather benign. Question, many cake keywords come in a = negated form e.g. no-ack-filter, so one would expect NOWASHNQB to also = come in the form WASHNQB to only wash NQB? Regards Sebastian >=20 >=20 > --=20 > Oct 30: = https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html > Dave T=C3=A4ht CSO, LibreQos > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake