From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test/crypto: remove crypto perf tests
Date: Tue, 11 Jul 2017 10:54:52 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBD9DC3@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1686914.0vIiBvB1W8@xps>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Saturday, July 8, 2017 6:04 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; Doherty, Declan <declan.doherty@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] test/crypto: remove crypto perf tests
>
> 15/05/2017 21:57, Pablo de Lara:
> > Since the crypto perf application is flexible enough to cover all the
> > crypto performance tests, these are not needed anymore, so they will
> > be removed to avoid duplications.
> > Besides, the crypto perf application gives the user more options to
> > get performance, for every single supported algorithm, such as varying
> > the buffer size as the user wants.
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> What is the status of this patch?
Sorry, I forgot about this. We were going to remove these tests, since we thought
that the crypto-perf app was mature enough, but we have found out
that for some cases (mainly when using hardware devices), the measurements
in that application are not realistic (the app was tuned for software
Therefore, I will defer this patch for the next release, when we should cover
these cases in the crypto-perf app.
Thanks,
Pablo
next prev parent reply other threads:[~2017-07-11 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 19:57 Pablo de Lara
2017-07-08 17:03 ` Thomas Monjalon
2017-07-11 10:54 ` De Lara Guarch, Pablo [this message]
2017-10-04 6:48 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2017-10-05 9:34 ` Zhang, Roy Fan
2017-10-05 13:02 ` Akhil Goyal
2017-10-05 13:34 ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CBD9DC3@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).