Re: [dpdk-dev] [PATCH v3 0/8] examples/ipsec-secgw: make app to use ipsec library

[Radu Nicolau <radu.nicolau@intel.com>]

On 12/6/2018 3:54 PM, Konstantin Ananyev wrote:
> This patch series depends on the patch series:
>
> Add 'try' semantics for RD and WR locking
> http://patches.dpdk.org/patch/48044/
> http://patches.dpdk.org/patch/48045/
>
> ipsec: new library for IPsec data-path processing
> http://patches.dpdk.org/patch/48566/
> http://patches.dpdk.org/patch/48567/
> http://patches.dpdk.org/patch/48568/
> http://patches.dpdk.org/patch/48569/
> http://patches.dpdk.org/patch/48570/
> http://patches.dpdk.org/patch/48571/
> http://patches.dpdk.org/patch/48572/
> http://patches.dpdk.org/patch/48573/
> http://patches.dpdk.org/patch/48574/
>
> to be applied first.
>
> v2 -> v3
>   - add IPv6 cases into test scripts
>   - fixes for IPv6 support
>   - fixes for inline-crypto support
>   - some code restructuring
>
> v1 -> v2
>   - Several bug fixes
>
> That series contians few bug-fixes and changes to make ipsec-secgw
> to utilize librte_ipsec library:
>       - changes in the related data structures.
>       - changes in the initialization code.
>       - changes in the data-path code.
>       - new command-line parameters to enable librte_ipsec codepath
>         and related features.
>       - test scripts to help automate ipsec-secgw functional testing.
>
> Note that right now by default current (non-librte_ipsec) code-path
> will be used. User has to run application with new command-line option
> ('-l')
> to enable new codepath.
> The main reason for that:
>    - current librte_ipsec doesn't support all ipsec algorithms
>      and features that the app does.
>    - allow users to run both versions in parallel for some time
>      to figure out any functional or performance degradation with the
>      new code.
>
> Test scripts were run with the following crypto devices:
>   - aesni_mb
>   - aesni_gcm
>   - qat
>
Series Acked-by: Radu Nicolau <radu.nicolau@intel.com 
<mailto:radu.nicolau@intel.com>>