From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=4MfZTZU1c43UuRcJA45CG6pdOm/EEVxDhW4nWAbtEt0=; b=uG0Po7L3h2f9NJhidlPmX+s0BYBiB7HBA8GcHB/TDEDj/qNkLudRWyoB6oLVIGfe2K kCReYH5B4Wwvjn6/HDGC04mc53UGdRpCq+Iq7gIh0iAEUrSg0SqARID3NwFW5GNV9spW HREoEwzDRdqm5Ya8MU0Z9BbSn9adn+9FNlUUP8T5TkbdVnHF+z65io0S+qoakRO4cVet Y5Ywb8cgCmmN2QS+TpGR+q9Sh1DkphSYXbWK226hIH2gfXveQeS/mT3Ss0LE4iQphhPm KGxYfYgi5pZjhk5W/3CM/sOpLgrMKgcLOx3ETuLvwrS9muJMWznYAPAkNZrs7jCjNOEa Ln+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=4MfZTZU1c43UuRcJA45CG6pdOm/EEVxDhW4nWAbtEt0=; b=dya8deinGegqZF2jwkYqfDsEp7bs7O10c47gmtMW9iSal7UMGmjcYebB0f/cxkpwDt 78q2GCTS73RJ3lZQELOV5rnGkOVNAo2YbOgG55Vy9TFxHiPm5vQvrAbxGh2nQvbPHXWB xWxjBZ+NXdjbuMzmud0TII6KhSi40RiGeXAvPxqfrNLwEmDmyvL+0m7PtsHjWnN6oTOZ 4zerDFaxvRezsZWGZFjlT+l+Q3NsYCqN4x55g9RvVUPxEQtGDCurA9AnfIC04NWhtvmT 6NEHBzvB13mKXNXbUv/1qA6U01Cka02WCrofJmIqSr15Uz+G6izeKvZ3uulqfHyU2oGf nDgw== X-Gm-Message-State: AIkVDXKrCRhql1Kqelo/JxNoqTgu2vUIBMI+QkL9hKI0UZ2EffJ46o/UFOlBuTcs2odLFSUG X-Received: by 10.223.164.203 with SMTP id h11mr8746673wrb.153.1484851561006; Thu, 19 Jan 2017 10:46:01 -0800 (PST) Received: from 6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id d64sm110244wmh.3.2017.01.19.10.45.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Jan 2017 10:45:59 -0800 (PST) Date: Thu, 19 Jan 2017 19:45:52 +0100 From: Adrien Mazarguil To: Thomas Monjalon Cc: Yong Liu , dev@dpdk.org 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 Content-Disposition: inline In-Reply-To: <2857373.EhiM2j9T0R@xps13> Subject: Re: [dpdk-dev] [PATCH] doc: announce ABI change for cloud filter 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, 19 Jan 2017 18:46:01 -0000 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