From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shards.monkeyblade.net (shards.monkeyblade.net [184.105.139.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C1A033B29E for ; Wed, 23 May 2018 16:04:05 -0400 (EDT) Received: from localhost (pool-173-77-163-54.nycmny.fios.verizon.net [173.77.163.54]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 8482A144E93B9; Wed, 23 May 2018 13:04:04 -0700 (PDT) Date: Wed, 23 May 2018 16:04:03 -0400 (EDT) Message-Id: <20180523.160403.20551254565100734.davem@davemloft.net> To: chromatix99@gmail.com Cc: toke@toke.dk, cake@lists.bufferbloat.net, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org From: David Miller In-Reply-To: <91739F64-20B7-4C56-A7A3-AB8C71B9437C@gmail.com> References: <152699745846.21931.4558451708304709296.stgit@alrua-kau> <20180523.144442.864194409238516747.davem@davemloft.net> <91739F64-20B7-4C56-A7A3-AB8C71B9437C@gmail.com> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Wed, 23 May 2018 13:04:04 -0700 (PDT) Subject: Re: [Cake] [PATCH net-next v15 4/7] sch_cake: Add NAT awareness to packet classifier 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, 23 May 2018 20:04:05 -0000 From: Jonathan Morton Date: Wed, 23 May 2018 22:31:53 +0300 > Remember that it takes two different qdiscs to implement ingress and > egress on the same physical interface, and there's no obvious > logical link between them - especially since the ingress one has to > be attached to an ifb, not to the actual interface, because there's > no native support for ingress qdiscs. Who said anything about using an ingress qdisc to record/remember this information?