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 032953BA8E for ; Wed, 30 May 2018 16:50:11 -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=1527713411; bh=xICoktsl2e6BEluGjkYOv1ZP44ul3iImTKNZTFD5Nqc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ODrSswZk4Z6rDfazY/ZtE46gjecp5Ibun0XfExu8KFOs08PCdZ6mRFfEzz+WrO6kI t2B5kzXTd5v9kRmZ41fQb79yOF7R7uw5WFTnmezrcf+GfLcKL9/bPVgCUo+TCEmxAI UCEG664PTTxQZ+3UeRr0maiv56fpSksFcOfLcMrtuhR0vZc+RwzTrJjfehHH4Qc8FT k3nWjTWvkKventxwbhEjrISTClXrUUEtqb2W0PE7L1LAxwWLiaeEPnLPfe7TBB565p e83b+3adbjgQlw2bxRL1FUPR1mqKYsaSFAslGliAobk3AVLjhzil5atZIKswEYpBYv E8p7MbVxu4s5Q== To: Dave Taht Cc: Georgios Amanakis , Cake List In-Reply-To: References: <87muwyy34k.fsf@toke.dk> <87tvqoc3vl.fsf@toke.dk> <87r2lsc2dm.fsf@toke.dk> Date: Wed, 30 May 2018 22:50:15 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87efhsc1h4.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] Fwd: Does the latest cake support "tc filter"? 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: Wed, 30 May 2018 20:50:12 -0000 Dave Taht writes: > I also worry that the new tc filter related code is going to cause > weirdness from other subsystems and deployments. Someone (for example) > sets iptables priorities or something else for some other reason to > make a set of iptables rules work (the skb-priority field is so > massively overloaded), and that messes up what cake wants. > > this is why I elided tc filters entirely all those years ago. I guess > the MAJ approach toke took is sufficient. Yeah. Stole that from fq_codel, actually. That allows you to select a queue using the priority field as well as with an explicit classifier (with the same major number check). So guess that is relatively safe :) -Toke