From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 25BE3CFA2 for ; Thu, 9 Mar 2017 16:29:04 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Mar 2017 07:29:04 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,136,1486454400"; d="scan'208";a="1140069787" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.255.86.60]) ([10.255.86.60]) by fmsmga002.fm.intel.com with ESMTP; 09 Mar 2017 07:29:02 -0800 To: Pascal Mazon , keith.wiles@intel.com References: Cc: dev@dpdk.org From: Ferruh Yigit Message-ID: <990c6cd5-9767-3dd4-b499-295eb8b4c8fa@intel.com> Date: Thu, 9 Mar 2017 15:29:01 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v3 3/4] net/tap: add netlink back-end for flow API X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Mar 2017 15:29:05 -0000 On 3/7/2017 4:35 PM, Pascal Mazon wrote: > Each kernel netdevice may have queueing disciplines set for it, which > determine how to handle the packet (mostly on egress). That's part of > the TC (Traffic Control) mechanism. This is nice. qdisc is egress part of the network stack right, is there any ingress part of it? > > Through TC, it is possible to set filter rules that match specific > packets, and act according to what is in the rule. This is a perfect > candidate to implement the flow API for the tap PMD, as it has an > associated kernel netdevice automatically. > > Each flow API rule will be translated into its TC counterpart. What can be use cases here? > > To leverage TC, it is necessary to communicate with the kernel using > netlink. This patch introduces a library to help that communication. > What do you think implementing these out of tap PMD? These can be used by KNI too. > Inside netlink.c, functions are generic for any netlink messaging. > Inside tcmsgs.c, functions are specific to deal with TC rules. > > Signed-off-by: Pascal Mazon > Acked-by: Olga Shern <...>