From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v4 0/3] use architecure independent macros
Date: Wed, 9 Jan 2019 22:09:13 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89780361B49@irsmsx112.ger.corp.intel.com> (raw)
In-Reply-To: <20181220115645.37584-1-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Thursday, December 20, 2018 11:57 AM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Subject: [PATCH v4 0/3] use architecure independent macros
>
> 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>
Series applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2019-01-09 22:09 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 ` [dpdk-dev] [PATCH v4 0/3] use architecure independent macros Fan Zhang
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 ` De Lara Guarch, Pablo [this message]
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=E115CCD9D858EF4F90C690B0DCB4D89780361B49@irsmsx112.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).