[L4s-discuss] dualpi2 & iproute2 - how to get latest L4S ECN coupled dual queue?

rjmcmahon <rjmcmahon@rjmcmahon.com> Tue, 12 September 2023 20:46 UTC

Return-Path: <rjmcmahon@rjmcmahon.com>
X-Original-To: l4s-discuss@ietfa.amsl.com
Delivered-To: l4s-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 284FDC1519B7 for <l4s-discuss@ietfa.amsl.com>; Tue, 12 Sep 2023 13:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=rjmcmahon.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RNuiWVLtYe83 for <l4s-discuss@ietfa.amsl.com>; Tue, 12 Sep 2023 13:46:40 -0700 (PDT)
Received: from bobcat.rjmcmahon.com (bobcat.rjmcmahon.com [45.33.58.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2704DC15199B for <l4s-discuss@ietf.org>; Tue, 12 Sep 2023 13:46:39 -0700 (PDT)
Received: from mail.rjmcmahon.com (bobcat.rjmcmahon.com [45.33.58.123]) by bobcat.rjmcmahon.com (Postfix) with ESMTPA id 3C39F1B25F for <l4s-discuss@ietf.org>; Tue, 12 Sep 2023 13:46:39 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bobcat.rjmcmahon.com 3C39F1B25F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rjmcmahon.com; s=bobcat; t=1694551599; bh=yvItR7L7OqyXPFpiLzXrv89ripvlmDpKxYfwO4yaSwU=; h=Date:From:To:Subject:From; b=BpTv9QsUQ6ZauIt4S+6Wxu4cxPRSpRY2hT4roBmzKtNCtduHx3ioqFBSnpl8RAMtk oguh8GN9yfbUU1bZ4OmPNTserp4T759QopdfiGmSStApW5G3o3Qno2vqzGFQ2QyEOL f5IAb/utt55+amI/qA2FkcbRKzmYkM49txsWHmHY=
MIME-Version: 1.0
Date: Tue, 12 Sep 2023 13:46:39 -0700
From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: l4s-discuss@ietf.org
Message-ID: <f61972f2ccd69addef76002053a91237@rjmcmahon.com>
X-Sender: rjmcmahon@rjmcmahon.com
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/l4s-discuss/k7jNt-CM8EdZ3arHy0F84xAbIBA>
Subject: [L4s-discuss] dualpi2 & iproute2 - how to get latest L4S ECN coupled dual queue?
X-BeenThere: l4s-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Low Latency, Low Loss, Scalable Throughput \(L4S\) " <l4s-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l4s-discuss>, <mailto:l4s-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l4s-discuss/>
List-Post: <mailto:l4s-discuss@ietf.org>
List-Help: <mailto:l4s-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l4s-discuss>, <mailto:l4s-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Sep 2023 20:46:44 -0000

Hi All,

I'm confused about how to best try dualpi2 on a modern kernel, e.g. 
Fedora 38, in a lab environment

[rjmcmahon@fedora iproute2-6.5.0]$ uname -r
6.4.12-200.fc38.x86_64

It looks that the code for tc qdisc dualpie2 (via ipoute2) is not 
released from kernel.org

https://git.kernel.org/pub/scm/network/iproute2/iproute2.git

The following web site looks inactive for years - is this the latest 
code and, if so, what's the debian released that it best matches?

https://github.com/L4STeam/iproute2

Finally, I noticed Broadcom Jericho 3 merchant silicon DNX family has 
L4S ECN marking & couple dual queue support but I don't seem to be able 
to find a system integrator supporting it. (Maybe the generative AI is 
causing network engineers to ignore billions of end users and their 
devices that require low latency services?)

Thanks,
Bob