From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Cc: akhil.goyal@nxp.com, pablo.de.lara.guarch@intel.com
Subject: [dpdk-dev] [PATCH v4 0/3] use architecure independent macros
Date: Thu, 20 Dec 2018 11:56:42 +0000 [thread overview]
Message-ID: <20181220115645.37584-1-roy.fan.zhang@intel.com> (raw)
In-Reply-To: <20181219201609.37934-1-roy.fan.zhang@intel.com>
This patch updates the aesni_mb to use IMB_* arch independent macros to
reduce the code size and future maintaining effort.
In intel-ipsec-mb library 0.52 all supported algorithms now have the IMB_*
arch independent macros enabled. The macros help reducing the application's
code size and remove the burden of maintaining the support to different
architectures such as SSE and AVX*, etc.
This patch adds this support into AESNI-MB PMD. Meanwhile to keep
supporting the older version of intel-ipsec-mb library, the existing
rte_aesni_mb_pmd*.c are renamed to rte_aesni_mb_pmd*_compat.c and the
compiler will check the version number in /usr/include/inte-ipsec-mb.h and
decides which files to be compiled. For intel-ipsec-mb library 0.52 the
rte_aesni_mb_pmd*.c will be compiled. For the older version
rte_aesni_mb_pmd*_compat.c will be compiled.
It is planned to change the minimum intel-ipsec-mb support version to 0.52
in DPDK 19.05 release. By then all code intended for supporting older
version will be removed, including rte_aesni_mb_pmd*_compat.c.
Acked-by: Damian Nowak <damianx.nowak@intel.com>
v4:
- combined documentation patches into one.
- updated release note.
v3:
- patch split.
- fixed meson build bug.
- updated commit message.
- updated documentation.
v2:
- making the PMD compatible with both new intel-ipsec-mb version 0.52 and older
- fixed a bug
Fan Zhang (3):
crypto/aesni_mb: rename files
crypto/aesni_mb: use architecture independent macros
doc: update documentation
doc/guides/cryptodevs/aesni_mb.rst | 4 +-
doc/guides/rel_notes/deprecation.rst | 3 +
doc/guides/rel_notes/release_19_02.rst | 3 +
drivers/crypto/aesni_mb/Makefile | 26 +-
drivers/crypto/aesni_mb/meson.build | 18 +-
drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 190 ++-
drivers/crypto/aesni_mb/rte_aesni_mb_pmd_compat.c | 1239 ++++++++++++++++++++
drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 86 +-
.../crypto/aesni_mb/rte_aesni_mb_pmd_ops_compat.c | 719 ++++++++++++
drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h | 52 +-
10 files changed, 2169 insertions(+), 171 deletions(-)
create mode 100644 drivers/crypto/aesni_mb/rte_aesni_mb_pmd_compat.c
create mode 100644 drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops_compat.c
--
2.13.6
next prev parent reply other threads:[~2018-12-20 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 14:04 [dpdk-dev] [PATCH] crypto/aesni_mb: use of archtecture " Fan Zhang
2018-12-11 12:29 ` [dpdk-dev] [PATCH v2] crypto/aesni_mb: use architure independent marcos Fan Zhang
2018-12-18 10:26 ` Akhil Goyal
2018-12-19 13:08 ` Thomas Monjalon
2018-12-19 13:48 ` Zhang, Roy Fan
2018-12-19 20:16 ` [dpdk-dev] [PATCH v3 0/4] use architecure independent macros Fan Zhang
2018-12-19 20:16 ` [dpdk-dev] [PATCH v3 1/4] crypto/aesni_mb: rename files to compatible Fan Zhang
2018-12-19 20:16 ` [dpdk-dev] [PATCH v3 2/4] crypto/aesni_mb: use architecture independent macros Fan Zhang
2018-12-19 20:16 ` [dpdk-dev] [PATCH v3 3/4] doc: update library support version Fan Zhang
2018-12-19 20:16 ` [dpdk-dev] [PATCH v3 4/4] doc: update deprecation notice Fan Zhang
2018-12-20 11:56 ` Fan Zhang [this message]
2018-12-20 11:56 ` [dpdk-dev] [PATCH v4 1/3] crypto/aesni_mb: rename files Fan Zhang
2018-12-20 11:56 ` [dpdk-dev] [PATCH v4 2/3] crypto/aesni_mb: use architecture independent macros Fan Zhang
2018-12-20 11:56 ` [dpdk-dev] [PATCH v4 3/3] doc: update documentation Fan Zhang
2019-01-09 22:09 ` [dpdk-dev] [PATCH v4 0/3] use architecure independent macros 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=20181220115645.37584-1-roy.fan.zhang@intel.com \
--to=roy.fan.zhang@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
/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).