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 41EA63CB3F for ; Thu, 17 May 2018 06:42:53 -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=1526553772; bh=ewZpmAWfX1Gc2iXRPUp+FQLMiIAsMa9yTEjXMWDiMyI=; h=From:To:Subject:In-Reply-To:References:Date:From; b=TncNoZhoOok75RQwMWPZqRLFpF/zporNPIz0lZdcApl9BQZBqmHgZfQSINHxRTVKK nb+yDrYyE5RXEZAfBD7LS4VDFDxbSS8dS48HhwN4kb3yRjcdWg7tmsFA5rhofkl0lA GbAAUP8bCQn/t6v5AJov5mklA5pjqT62PXkc0LeykxwjG4H3q1cU2eodRBmsRnjHfa rVIHkvWslA9xN2mQsc0yWcn+7Uu5S1OzUiveMfTX8ugLBJT4PxJEWa97XqmSXy+Hll dGmbuj0cTgCHDozeNXy+SIHvSjjQc5NS4YlbEDDMWZihjf3J8bF4IA/Vd3pRzM++ct iQR+2FxzDgtSQ== To: Fushan Wen , cake@lists.bufferbloat.net In-Reply-To: References: Date: Thu, 17 May 2018 12:42:51 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87muwyy34k.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] 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: Thu, 17 May 2018 10:42:53 -0000 Fushan Wen writes: > Hello developers, > I've seen the mail in the netdev mailing list, saying "other tc > filters supported". So can I use "tc filter" to attach specified > traffic to a specified tin without DSCP marks? It's helpful when > dealing with ingress traffic where iptables DSCP mark won't work. Yes, the version submitted to upstream supports this. You can override which tin packets goes in by setting skb->priority from a filter or application (the major number needs to be set to the qdisc ID, and the minor number becomes the tin to queue packets in). However, these changes have not been backported, so they are not available in the cobalt branch. You can pull them from the upstream-4.18 branch instead. That should build against a current net-next tree, and possibly a bit older. Alternatively, you can pull the current patches from patchwork and use those. Or wait for a backport after we're done with the upstream submission :) -Toke