From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>,
John Daley <johndale@cisco.com>,
Hyong Youb Kim <hyonkim@cisco.com>,
Gaetan Rivet <gaetan.rivet@6wind.com>,
Beilei Xing <beilei.xing@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>, Matan Azrad <matan@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>,
John McNamara <john.mcnamara@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Harry van Haaren <harry.van.haaren@intel.com>,
Xiaoyun Li <xiaoyun.li@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ethdev: deprecate legacy filter API
Date: Wed, 17 Apr 2019 08:59:56 +0300 [thread overview]
Message-ID: <583e48d0-8c77-9217-4945-06593560375f@solarflare.com> (raw)
In-Reply-To: <AM0PR0502MB37956D6E641A2AD0E181DF92C3250@AM0PR0502MB3795.eurprd05.prod.outlook.com>
On 4/17/19 8:41 AM, Shahaf Shuler wrote:
> Wednesday, April 17, 2019 3:36 AM, Thomas Monjalon:
>> Subject: [PATCH] ethdev: deprecate legacy filter API
>>
>> As stated in the deprecation notice from December 2016, "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)".
>>
>> After a long wait of more than two years, the legacy filter API is marked as
>> deprecated, while still tested with testpmd and the tep_termination
>> example.
>>
>> The next step will be to announce a deadline for complete removal.
>> As preparation of the removal of rte_eth_ctrl.h, RTE_ETH_FLOW_*,
>> RTE_TUNNEL_TYPE_* and RTE_ETH_HASH_FUNCTION_* definitions are
>> moved to rte_ethdev.h and rte_flow.h.
>>
>> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Acked-by: Shahaf Shuler <shahafs@mellanox.com>
>
> It's about time 😊.
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2019-04-17 6:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 0:36 Thomas Monjalon
2019-04-17 0:36 ` Thomas Monjalon
2019-04-17 5:41 ` Shahaf Shuler
2019-04-17 5:41 ` Shahaf Shuler
2019-04-17 5:59 ` Andrew Rybchenko [this message]
2019-04-17 5:59 ` Andrew Rybchenko
2019-04-17 6:00 ` Jerin Jacob Kollanukkaran
2019-04-17 6:00 ` Jerin Jacob Kollanukkaran
2019-04-17 16:54 ` Stephen Hemminger
2019-04-17 16:54 ` Stephen Hemminger
2019-04-18 9:24 ` [dpdk-dev] [EXT] " Hemant Agrawal
2019-04-18 9:24 ` Hemant Agrawal
2019-04-18 12:37 ` [dpdk-dev] " Adrien Mazarguil
2019-04-18 12:37 ` Adrien Mazarguil
2019-04-18 17:58 ` Ajit Khaparde
2019-04-18 17:58 ` Ajit Khaparde
2019-04-18 18:16 ` Ferruh Yigit
2019-04-18 18:16 ` Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=583e48d0-8c77-9217-4945-06593560375f@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=adrien.mazarguil@6wind.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gaetan.rivet@6wind.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=hyonkim@cisco.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=johndale@cisco.com \
--cc=matan@mellanox.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=shahafs@mellanox.com \
--cc=shreyansh.jain@nxp.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@intel.com \
--cc=xiaoyun.li@intel.com \
--cc=yskoh@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).