From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 185F33B29E for ; Sat, 20 Feb 2021 06:53:48 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1613822025; bh=R5tyFZi5LlV/pkBRCbZBEgDlUZkhNu2/iIwdY/A4gFM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ynu6kIKrQ6cmVm4WC6mHOI/VyGMaGGbEXeId5YwIYB2DtU04yR/HFJVzKSlYRFyR2 jCQa04tY2658HYUhzhyWxnjnX0EdGLZZ54HrKcKw1srUmPnHNyOQaCeUE/TTV9RxV3 VAW0U8OxrcS6xNEJTKj2PKvczfwsjdf0O4mlXxYzwHvWpx/6J5FGZS0kkd7xvjmsXV 1nZwqV4w6ztAPqH6uqjtFgF7X4z9YhrrR2tVK0k1F3iADvMjEKE5rsSbnX84WZg50+ +vtpUUEJ+p6Ix3iKBwf4CCLDnoVEhsb0g8ctGLMx9XOplOQzz6ujm9OUf/yGxXB4SW Hakik1Jvk7ljw== To: John Sager , Peter Lepeska Cc: cake@lists.bufferbloat.net In-Reply-To: <406344b9-49af-54f0-15fd-a17c5f3b604c@sager.me.uk> References: <87mtw1kx9c.fsf@toke.dk> <87im6pkweq.fsf@toke.dk> <9a889d98-0fae-d1af-6dea-c534f0df854a@sager.me.uk> <406344b9-49af-54f0-15fd-a17c5f3b604c@sager.me.uk> Date: Sat, 20 Feb 2021 12:53:45 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87im6nhs52.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] Enforcing video quality question 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: Sat, 20 Feb 2021 11:53:55 -0000 John Sager writes: > You will need to specify the hosts explicitly, unless you can live with them > all sharing one bandwidth class. In that case if you have more than one > using bandwidth they would share the bandwidth in that class equally. I > assume from your original post that you want each host to be limited in > bandwidth to a specific value, but to do that you need a class for each host > in the ingress HTB. Just do enough classes that you can cover the whole IP space? At least for IPv4 that's trivial; for IPv6 you'll probably need to hash and hope that there are not too many collisions... > What you probably need is a scheduler that has a limit per flow up to > an overall ceiling beyond which it shares equally. I'm not aware that > any of the schedulers do anything like that. If you use FQ-CoDel as the leaf qdisc in HTB you'll get flow scheduling to each host. There won't be a per-flow *limit*, but you'll get nice scheduling of all flows going towards each host. -Toke