From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 6B009A0096 for ; Thu, 11 Apr 2019 09:50:02 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6CB975F27; Thu, 11 Apr 2019 09:50:00 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 208A25F1F for ; Thu, 11 Apr 2019 09:49:59 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AFD0021D2B; Thu, 11 Apr 2019 03:49:57 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 11 Apr 2019 03:49:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding:content-type; s=mesmtp; bh=azTJtI+vHp 1WeN/lVKelP38BauyvXcV5pAbluBr5vr4=; b=l3tDkCe+eQouBRirQ7evb9IUYf BXws3p35rLRCX27UQUWvLOMgiZP4PI7XLAYVHxtmrL6FAOUh3QrUfJKeg0HeV8hd 3tn4yI0/z+KtNEdp4gZVAaE7Rxfuqpoa89qnaPe2A8L3qT8Fd8yipR60U/2R0MQT bZhNoHBX8MaC1ZhKs= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=azTJtI +vHp1WeN/lVKelP38BauyvXcV5pAbluBr5vr4=; b=OHXAyA+NfKm3b/dIylOK50 gl6lMyu8VuaZ6pyNn3RO2VW0JU87e7lW/5N5LKkpicSRiUe+Ftj/krIfdhAIJ/Ey lgMuvB2zUmZfsT+DTBP8C315OzQl7/suAOv4BvEPDRdt+XeWZY1vUgNkLUhqGpwP ZHHhh/Lu4yPWKkTUSuVIcw7Lz8Uu1VPj97+HgiFKkql5TpcQc/b1jyksDgK2SRqw m8Q/x1JoCgLkFePsxP2HJ+KJPFuES59A82DB1U0nD8LacWHhvn3M6TUW91tG6hzU V6dxMAnOPzjO3DNVwkB5u6sv4L1nCp0nt6bIFHRkyzhuSm1CUaShabeKXfJlT2AA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudekgdduudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkggfgtgesthfuredttd dtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhho nhhjrghlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtdefrddukeegnecurfgrrh grmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehl uhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 61299E43A3; Thu, 11 Apr 2019 03:49:56 -0400 (EDT) From: Thomas Monjalon To: ferruh.yigit@intel.com, arybchenko@solarflare.com Cc: dev@dpdk.org Date: Thu, 11 Apr 2019 09:49:54 +0200 Message-ID: <8025349.HGM0LRMdJy@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: [dpdk-dev] ethdev flow director/filtering/steering 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190411074954.QPZ2DVnWi8MTgONdHvJoqsCJ-fu2iedamYGnwDW4ifA@z> About the features called flow director, filtering or flow steering, we have some overlap in our API that we should clean. It is especially important when considering to freeze the API for stability. Please read this deprecation notice from December 2016: * ethdev: the legacy filter API, including ``rte_eth_dev_filter_supported()``, ``rte_eth_dev_filter_ctrl()`` as well as filter types MACVLAN, ETHERTYPE, FLEXIBLE, SYN, NTUPLE, TUNNEL, FDIR, HASH and L2_TUNNEL, is superseded by the generic flow API (rte_flow) in PMDs that implement the latter. Target release for removal of the legacy API will be defined once most PMDs have switched to rte_flow. We must mark the eth_dev_filter API as deprecated and decide about a date to remove it. Which PMD is implementing this API and not rte_flow? If there are still some, deadlines should help them to be converted :) If some help is needed, please ask. Anyway, after more than 2 years of notice, I think it is fair to mark the legacy API as deprecated in 19.05 release.