From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Azarewicz, PiotrX T" <piotrx.t.azarewicz@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [PATCH v5] crypto/aesni_gcm: migration from MB library to ISA-L
Date: Mon, 16 Jan 2017 15:20:42 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2026B254E@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <5097630.aeECJvAXha@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, January 16, 2017 2:42 PM
> To: Azarewicz, PiotrX T <piotrx.t.azarewicz@intel.com>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> Doherty, Declan <declan.doherty@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v5] crypto/aesni_gcm: migration from MB
> library to ISA-L
>
> 2017-01-16 13:37, Piotr Azarewicz:
> > v5 changes:
> > - rebase on top of dpdk-next-crypto
> > - remove the perftest output from commit message
> > - correction in aesni_gcm.rst
> > - fix typo
>
> Why have you removed the perftest output?
> Because it is not in favor of this patch?
Hi,
We removed the performance results because we are not allowed to publish them publically without legal approval.
Also, and more importantly, the perftest results aren't reliable which is one of the reasons that we are developing the new dpdk-test-crypto-perf app (patch submitted).
Using the newer app we are seeing more of less the same performance, slightly higher for some packets sizes, slightly lower for some others.
John.
next prev parent reply other threads:[~2017-01-16 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 18:53 [PATCH v2] crypto/aesni_gcm: migration from MB library to ISA-L Michal Jastrzebski
2017-01-03 13:02 ` [PATCH v3] " Piotr Azarewicz
2017-01-03 14:14 ` Thomas Monjalon
2017-01-05 13:51 ` [PATCH v4] " Piotr Azarewicz
2017-01-05 15:12 ` Thomas Monjalon
2017-01-16 12:37 ` [PATCH v5] " Piotr Azarewicz
2017-01-16 14:42 ` Thomas Monjalon
2017-01-16 15:20 ` Mcnamara, John [this message]
2017-01-16 14:43 ` Thomas Monjalon
2017-01-17 7:42 ` Azarewicz, PiotrX T
2017-01-16 16:05 ` Declan Doherty
2017-01-17 11:19 ` [PATCH v6 0/2] " Piotr Azarewicz
2017-01-17 11:19 ` [PATCH v6 1/2] " Piotr Azarewicz
2017-01-17 11:19 ` [PATCH v6 2/2] app/test: add GCM additional tests Piotr Azarewicz
2017-01-18 12:37 ` [PATCH v6 0/2] crypto/aesni_gcm: migration from MB library to ISA-L 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=B27915DBBA3421428155699D51E4CFE2026B254E@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=piotrx.t.azarewicz@intel.com \
--cc=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.