On 02/12/16 10:37, Thomas Monjalon wrote:
2016-12-02 09:46, Declan Doherty:
Add new initialisation option to the aesni_mb_pmd to allow the user to specify
which set of SIMD functions to load from the AESNI Multi-Buffer Crypto for IPsec
library.
Why let user choose? Isn't the most recent the better?
This PMD and other software crypto PMDs could (should?) override the CFLAGS
like rte_acl do, in order to be able to use recent SIMD functions even if it
was globally disabled by the compilation target.
See my comment in the rte_memset thread.
In general yes, I was mainly using this to allow quick performance
comparisons between different platforms and different instruction sets
on the same platform without recompilation, but I admit that this is
probably not a normal end user use case.
I'll look at the CFLAGS options you mention and address in a V2.
