[dpdk-dev] [RFC] doc: deprecate legacy code path in ipsec-secgw

[Akhil Goyal]

Hi Bernard,

> All the functionality of the legacy code path in now available in
> the librte_ipsec library. It is planned to deprecate the legacy
> code path in the 19.11 release and remove the legacy code path in
> the 20.02 release.
> 
> Signed-off-by: Bernard Iremonger <bernard.iremonger at intel.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index a7796f4..258fee8 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -82,3 +82,8 @@ Deprecation Notices
>    to set new power environment if power environment was already initialized.
>    In this case the function will return -1 unless the environment is unset first
>    (using ``rte_power_unset_env``). Other function usage scenarios will not
> change.
> +
> +* ipsec-secgw: All the ipsec-secgw legacy code path functionality is now
> +  available in the librte_ipsec library. It is planned to deprecate the legacy
> +  code path in the ipsec-secgw application in the 19.11 release and remove it
> +  in the 20.02 release.
> --
Library mode path was impacting the performance on NXP platforms for lookaside mode at the time the library was introduced. Not sure what is the state today. We will evaluate the performance numbers when the actual code will be submitted for review. If the numbers are good we can remove the legacy code path. Apart from this concern,
Acked-by: Akhil Goyal <akhil.goyal at nxp.com>

This patch is an RFC patch and generally RFC patches are not merged.
Please send the patch again without the RFC tag, if this patch need to be integrated in this release.
You can take the Acks.

Regards,
Akhil