In current codes, tunnel configuration information is not stored in a device configuration, and it will get nothing if application want to retrieve tunnel config, so I think it is necessary to add rte_eth_dev_tunnel_configure() function is to do the configurations including flow and classification information and store it in a device configuration.
And tunneling packet encapsulation operation will benifit from the change. v2 change: Add more description for the change. Signed-off-by: Jijiang Liu <jijiang.liu at intel.com> --- doc/guides/rel_notes/deprecation.rst | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 5c458f2..df10249 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -23,3 +23,8 @@ Deprecation Notices * ABI changes are planned for struct rte_eth_tunnel_flow in order to extend new fileds to support tunneling packet configuration in unified tunneling APIs. The release 2.2 does not contain these ABI changes, but release 2.3 will, and no backwards compatibility is planned. + +* ABI changes are planned for struct rte_eth_conf in order to support tunnel configuration using unified tunneling APIs, + which is the rte_eth_dev_tunnel_configure(uint8_t port_id, rte_eth_tunnel_conf * tunnel_conf) + API is planned to add. And the 'tunnel_conf' shloud be stored in global 'rte_eth_conf'. + The release 2.2 does not contain these ABI change, but release 2.3 will, and no backwards compatibility is planned. -- 1.7.7.6
