DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Declan Doherty <declan.doherty@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] crypto/aesni_mb: add new option to select SIMD mode
Date: Fri, 02 Dec 2016 11:37:51 +0100	[thread overview]
Message-ID: <2408315.PI9TjJa4bq@xps13> (raw)
In-Reply-To: <1480671985-3677-3-git-send-email-declan.doherty@intel.com>

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.

  reply	other threads:[~2016-12-02 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02  9:46 [dpdk-dev] [PATCH 0/2] enablement of avx512 instruction support in aesni_mb_pmd Declan Doherty
2016-12-02  9:46 ` [dpdk-dev] [PATCH 1/2] crypto/aesni_mb: enablement of avx512 support in IPsec_mb library Declan Doherty
2016-12-02  9:46 ` [dpdk-dev] [PATCH 2/2] crypto/aesni_mb: add new option to select SIMD mode Declan Doherty
2016-12-02 10:37   ` Thomas Monjalon [this message]
2016-12-02 16:05     ` Declan Doherty
2016-12-21 22:04 ` [dpdk-dev] [PATCH v2] enablement of avx512 instruction support in aesni_mb_pmd Declan Doherty
2016-12-21 22:05   ` [dpdk-dev] [PATCH v2] crypto/aesni_mb: enablement of avx512 support in IPsec_mb library Declan Doherty
2016-12-22  8:26     ` De Lara Guarch, Pablo
2017-01-04 12:54       ` De Lara Guarch, Pablo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2408315.PI9TjJa4bq@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).