From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2001:470:dc45:1000::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C93693B29E for ; Mon, 16 Jul 2018 05:25:01 -0400 (EDT) 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=1531733100; bh=/VNqW/fU9e4zKX4GFIpYy+YO4kCHiGsi1cV+4VCm/RA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=V/q+2EDvw8oVbmOtOuP0JencuWMPrNB5O7cKOZWKCj3M8ghnZfJqVc0zeeOFN4gKi 3ZPkOxRmd5ht8gVapm+gipunZZiTQWWj1jrTJdRiKF9uWKRX/PwcIBQ3+n5AWO2Ena CIA/z+dU6tpnX9CwLo9qIj0/JqJhVcqdMA7udoMelQiuF0Zpd28MB3APtm+CcHsOC+ ualDmFYvCoqBSF/0Z30MIu7RuXfvpePnl1HwUO5tE9joK5vukP08RCvXLXZdKuXo01 jw07tRjesKGWNdg9JUkbuPJIVD8A2NYW0/mndlGPJmSJYrbq1TLJHTJzJss3zW0WP+ SLA5mvCDfgBgg== To: Dave Taht , Jonathan Morton Cc: Cake List In-Reply-To: References: <8736wla3lq.fsf@toke.dk> <4C12C6A1-84E3-4B78-885F-F5C212CD13FF@darbyshire-bryant.me.uk> <87wotw96el.fsf@toke.dk> <83B2AEF4-C052-444F-8AFA-E8C3EE2F4A7F@darbyshire-bryant.me.uk> <87wotw6yeo.fsf@toke.dk> Date: Mon, 16 Jul 2018 11:24:55 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87r2k37ct4.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] Backporting 'tc class' support 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: Mon, 16 Jul 2018 09:25:02 -0000 Dave Taht writes: > I am curious if the new tc class support would allow for recognizing > sebastian's desire to have the llc (?) dsl control packets moved to > the higher priority tin? > > Similarly, there were other things in early-sqm (like deprioritizing > ping, prioritizing dns) that I liked, but disliked using iptables to > use. You can write a tc filter in BPF, which allows you to do arbitrary matching on packet data... So as long as the packets go through the qdisc, the answer would be yes :) > lastly, the hopelessly overloaded skb->priority field is hopefully > still not recognized for anything that actually sets skb->priority > naively? CAKE will only react to the priority field if the upper 16 bits match the major number of the qdisc; so anything that sets priority has to know about the qdisc configuration for it to stick... -Toke