From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrien Mazarguil Subject: Re: [PATCH] doc: announce ABI change for cloud filter Date: Thu, 19 Jan 2017 19:45:52 +0100 Message-ID: <20170119184552.GB3779@6wind.com> References: <1484804043-50156-1-git-send-email-yong.liu@intel.com> <2857373.EhiM2j9T0R@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Yong Liu , dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id 4FC1DFA5A for ; Thu, 19 Jan 2017 19:46:01 +0100 (CET) Received: by mail-wm0-f43.google.com with SMTP id r126so6287156wmr.0 for ; Thu, 19 Jan 2017 10:46:01 -0800 (PST) Content-Disposition: inline In-Reply-To: <2857373.EhiM2j9T0R@xps13> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Jan 19, 2017 at 10:06:34AM +0100, Thomas Monjalon wrote: > 2017-01-19 13:34, Yong Liu: > > +* ABI changes are planned for 17.05: structure ``rte_eth_tunnel_filter_conf`` > > + will be extended with a new member ``vf_id`` in order to enable cloud filter > > + on VF device. > > I think we should stop rely on this API, and migrate to rte_flow instead. > Adrien any thought? I'm all for using rte_flow in any case. I've already documented an approach to convert TUNNEL filter rules to rte_flow rules [1], although it may be incomplete due to my limited experience with this filter type. We already know several tunnel item types must be added (currently only VXLAN is defined). I understand ixgbe/i40e currently map rte_flow on top of the legacy framework, therefore extending this structure might still be needed in the meantime. Not sure we should prevent this change as long as such rules can be configured through rte_flow as well. [1] http://dpdk.org/doc/guides/prog_guide/rte_flow.html#tunnel-to-eth-ipv4-ipv6-vxlan-or-other-queue -- Adrien Mazarguil 6WIND