From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F1AF83CB37 for ; Sat, 25 May 2024 07:15:35 -0400 (EDT) Received: by mail-lf1-x130.google.com with SMTP id 2adb3069b0e04-5296935252dso1663287e87.3 for ; Sat, 25 May 2024 04:15:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716635734; x=1717240534; darn=lists.bufferbloat.net; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Ys9HERCZ7dU/+DxTPL3Y/CKqPeP/ETFza6hWMs3+DiA=; b=mUC7EXcRykif42zIh4oGrjWjT9N9cZ9orcgZEam0PEK+mz9fmHTWSiHdfbUq1LuBUO dqreO4hOmI62PsGNIF85wW301t1bhI8S+JBdJZE/Uh1VSAbCOuTz4VRZriNBdJI0uVo9 NOELafMkSGX6LB99AfjO6pe1ixeji/4uyQUScgjJocYCP1qIJnbs5cyITOq0uGUel+uA +0v7MY/Xhs1I5eXG6YRICf9jtizh9Vrjk7XEDTiVEHY1eEmSzLvXs5LzK9yrZjkPpFzb wQg+vyzPbxlzAUCExmb/yiG/jrEgT5aNmll5iYyNMZ/PTQ7+9yDhtC8RLgyQSyuqVaEU bdKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716635734; x=1717240534; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Ys9HERCZ7dU/+DxTPL3Y/CKqPeP/ETFza6hWMs3+DiA=; b=aC37MenSDOPR/8sP9JLppjZu6z/KpbdpUc8W/1lgdB+WIKHoHJ7nMyog/n9ZCFhhcD CYda1ktwdJs6xNXYTk/QNLlTEdcs7dcsgDe7Enn/wqvaoCegRiaV0CKIxGYOV3Sxq+cG +HjPJ9c1haHY6f35cLaK1xmTo42uaBqQUNpGdt6dlHoWKwghu+AfQWduy1KJPR0CWFHx 7RIbkAIv9TrwkbmvrfEovbMM9P7D/g8v6Fx1yf0sQf0LlwYrWs/yJWcX8LG8ylZ6GLjn SOMtg8Oe7hmExJaXMJUS5BgdntelIzvRmu6OWVst8un246kM/psfiNxJXSHelaqLj0s+ t7HQ== X-Forwarded-Encrypted: i=1; AJvYcCVZKBBvox5fXIWQTe42vTZ7gQtahGSqjFk9bsOaX5d2voQGt92T1nGaa8rhrt2PU+CLNWA6px0aeKXM0K8xGhJFgufZKBFDJ+w+LlM= X-Gm-Message-State: AOJu0YzXaO6nK/vf39T0NuSvFG19a5sKKSDQ1qxhALS5OfBWEfhVyVaP ahcEu1jE8Fb2DJAVRjTeT/3pywBaBbUhJUG+Zzdy9TnmyET/fBBI X-Google-Smtp-Source: AGHT+IEbbbNoNQ5uQNDo4yGgn2eMQ1oJVSYjCBpnTmXHMjCbHLAKYhHprPTyOaSlDZl4X7piHqq9mQ== X-Received: by 2002:ac2:46fb:0:b0:51f:3fea:cbce with SMTP id 2adb3069b0e04-529668ca211mr2977920e87.51.1716635733843; Sat, 25 May 2024 04:15:33 -0700 (PDT) Received: from smtpclient.apple (37-33-193-139.bb.dnainternet.fi. [37.33.193.139]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-529a5dd44f9sm65625e87.224.2024.05.25.04.15.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 May 2024 04:15:33 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) From: Jonathan Morton In-Reply-To: Date: Sat, 25 May 2024 14:15:32 +0300 Cc: =?utf-8?Q?Linus_L=C3=BCssing?= , "bloat@lists.bufferbloat.net" Content-Transfer-Encoding: quoted-printable Message-Id: <1DA90C88-5762-43C4-84FF-51F4623D82CE@gmail.com> References: To: "Holland, Jake" X-Mailer: Apple Mail (2.3654.100.0.2.22) Subject: Re: [Bloat] Congestion control with FQ-Codel/Cake with Multicast? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 May 2024 11:15:36 -0000 > On 24 May, 2024, at 12:43 am, Holland, Jake via Bloat = wrote: >=20 > I agree with your conclusion that FQ systems would see different > streams as separate queues and each one could be independently > overloaded, which is among the reasons I don't think FQ can be > viewed as a solution here (though as a mitigation for the damage > I'd expect it's a good thing to have in place). Cake has the facility to override the built-in flow and tin = classification using custom filter rules. Look in the tc-cake manpage = under "OVERRIDING CLASSIFICATION". This could be applicable to = multicast traffic in two ways: 1: Assign all traffic with a multicast-range IP address to the Video = tin. Since Cake schedules by tin first, and only then by host and/or = flow, this should successfully keep multicast traffic from obliterating = best-effort and Voice tin traffic. 2: Assign all multicast traffic to a single flow ID (eg. zero), without = reassigning the tin. This will cause it all to be treated like a single = flow, giving the FQ mechanisms something to bite on. - Jonathan Morton=