From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cong Wang Subject: Re: [patch net-next 02/10] net: sched: introduce tcf block infractructure Date: Fri, 28 Apr 2017 10:48:34 -0700 Message-ID: References: <1493291540-2119-1-git-send-email-jiri@resnulli.us> <1493291540-2119-3-git-send-email-jiri@resnulli.us> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Linux Kernel Network Developers , David Miller , Jamal Hadi Salim , David Ahern , Eric Dumazet , Stephen Hemminger , Daniel Borkmann , Alexander Duyck , mlxsw@mellanox.com, Simon Horman To: Jiri Pirko Return-path: Received: from mail-wm0-f68.google.com ([74.125.82.68]:35032 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S642168AbdD1Rs4 (ORCPT ); Fri, 28 Apr 2017 13:48:56 -0400 Received: by mail-wm0-f68.google.com with SMTP id d79so12354990wmi.2 for ; Fri, 28 Apr 2017 10:48:55 -0700 (PDT) In-Reply-To: <1493291540-2119-3-git-send-email-jiri@resnulli.us> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Apr 27, 2017 at 4:12 AM, Jiri Pirko wrote: > From: Jiri Pirko > > Currently, the filter chains are direcly put into the private structures > of qdiscs. In order to be able to have multiple chains per qdisc and to > allow filter chains sharing among qdiscs, there is a need for common > object that would hold the chains. This introduces such object and calls > it "tcf_block". > What is filter chains sharing here? Sounds like a new feature you are trying to hide? How could it be possibly shared among qdisc's when they are still stored in a per-qdisc pointer? Look at tc actions, they can be shared because they are physically stored in a per-netns hashtable, filters can just refer them with indexes.