[ovs-dev] [RFC PATCH v2 07/10] Docs: Modify dpdk howto to include cryptodev.

[Chandran, Sugesh]

I followed this howto guide and managed to test the ipsec traffic on my board.
One comment as below.

Regards
_Sugesh


> -----Original Message-----
> From: ovs-dev-bounces at openvswitch.org [mailto:ovs-dev-
> bounces at openvswitch.org] On Behalf Of Ian Stokes
> Sent: Friday, August 25, 2017 5:40 PM
> To: dev at openvswitch.org
> Subject: [ovs-dev] [RFC PATCH v2 07/10] Docs: Modify dpdk howto to include
> cryptodev.
> 
> 
[Snip]
> +    $ export AESNI_MULTI_BUFFER_LIB_PATH=/opt/intel-ipsec-mb-0.45
> +
> +Compile DPDK as per usual.
> +
> +For use of crypto devs in OVS with DPDK the user is required to copy
> +``libIPSec_MB.a`` to the same location where the DPDK target libraries
> +OVS uses are stored. For example::
[Sugesh] Can we avoid this step to copy the lib to a DPDK location. Again this has
to be considered for the upstreaming of this series. Atleast if OVS can
pick up the lib from the env variable that would be great. 
Copying is not looking good from the usage point of view.
> +
> +    $ cp libIPSec_MB.a $DPDK_LOCATION/x86_64-native-linuxapp-gcc/lib/
> +
> +Compile OVS with DPDK as per usual.
> +
> +More information on the cryptodevs and their usage can be found in the
> +`DPDK docs <http://dpdk.org/doc/guides-
> 17.05/cryptodevs/index.html>`__.
> +
>  OVS with DPDK Inside VMs
>  ------------------------
> 
> --
> 1.7.0.7
> 
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev