From: Akhil Goyal <akhil.goyal@nxp.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "umesh.kartha@caviumnetworks.com"
<umesh.kartha@caviumnetworks.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"shally.verma@caviumnetworks.com"
<shally.verma@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: fix restore crypto op alignment and layout
Date: Tue, 19 Mar 2019 14:00:46 +0000 [thread overview]
Message-ID: <184efdc9-0ff7-f72d-3e1f-c539c52e7828@nxp.com> (raw)
In-Reply-To: <80054d6d-2110-8299-5a61-19ef8885ec8e@nxp.com>
On 3/19/2019 7:03 PM, Akhil Goyal wrote:
> Hi Konstantin,
>
> On 3/7/2019 7:43 PM, Konstantin Ananyev wrote:
>> in 18.08 new cache-aligned structure rte_crypto_asym_op was introduced.
>> As it also was included into rte_crypto_op, it caused implicit change
>> in rte_crypto_op layout and alignment: now rte_crypto_op is cahce-line
>> aligned has a hole of 40/104 bytes between phys_addr and sym/asym op.
>> It looks like unintended ABI breakage, plus such change can cause
>> negative performance effects:
>> - now status and sym[0].m_src lies on different cache-lines, so
>> post-process code would need extra cache-line read.
>> - new alignment causes grow of the space requirements and cache-line
>> reads/updates for structures that contain rte_crypto_op inside.
>> As there seems no actual need to have rte_crypto_asym_op cache-line
>> aligned, and rte_crypto_asym_op is not intended to be used on it's own -
>> the simplest fix is just to remove cache-line alignment for it.
>> As the immediate positive effect: on IA ipsec-secgw performance increased
>> by 5-10% (depending on the crypto-dev and algo used).
>> My guess that on machines with 128B cache-line and lookaside-protocol
>> capable crypto devices the impact will be even more noticeable.
>>
>> Fixes: 26008aaed14c ("cryptodev: add asymmetric xform and op definitions")
>>
>> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
>> ---
>> doc/guides/rel_notes/release_19_05.rst | 7 +++++++
>> lib/librte_cryptodev/Makefile | 2 +-
>> lib/librte_cryptodev/meson.build | 2 +-
>> lib/librte_cryptodev/rte_crypto_asym.h | 2 +-
>> 4 files changed, 10 insertions(+), 3 deletions(-)
>>
>> diff --git a/doc/guides/rel_notes/release_19_05.rst b/doc/guides/rel_notes/release_19_05.rst
>> index c0390ca16..ec2651b65 100644
>> --- a/doc/guides/rel_notes/release_19_05.rst
>> +++ b/doc/guides/rel_notes/release_19_05.rst
>> @@ -116,6 +116,13 @@ ABI Changes
>> Also, make sure to start the actual text at the margin.
>> =========================================================
>>
>> +* cryptodev: in 18.08 new structure ``rte_crypto_asym_op`` was introduced and
>> + included into ``rte_crypto_op``. As ``rte_crypto_asym_op`` structure was
>> + defined as cache-line aligned that caused unintended changes in
>> + ``rte_crypto_op`` structure layout and alignment. Remove cache-line
>> + alignment for ``rte_crypto_asym_op`` to restore expected ``rte_crypto_op``
>> + layout and alignment.
>> +
>>
> ABI version should be bumped in the release notes as well. I will update
> that while merging.
> Apart from that
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
>> Shared Library Versions
>> -----------------------
>>
Applied to dpdk-next-crypto
Thanks.
next prev parent reply other threads:[~2019-03-19 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 14:13 Konstantin Ananyev
2019-03-08 12:59 ` Trahe, Fiona
2019-03-12 12:04 ` Shally Verma
2019-03-19 13:33 ` Akhil Goyal
2019-03-19 13:33 ` Akhil Goyal
2019-03-19 14:00 ` Akhil Goyal [this message]
2019-03-19 14:00 ` Akhil Goyal
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=184efdc9-0ff7-f72d-3e1f-c539c52e7828@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=shally.verma@caviumnetworks.com \
--cc=umesh.kartha@caviumnetworks.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).