From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v3] app/test-crypto-perf: fix crypto operation resubmission
Date: Tue, 18 Apr 2017 15:26:01 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8974780BD3A@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8974780BD08@IRSMSX108.ger.corp.intel.com>
CC'ing stable@dpdk.org.
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch,
> Pablo
> Sent: Tuesday, April 18, 2017 4:24 PM
> To: Zhang, Roy Fan; dev@dpdk.org
> Cc: stable@dpdk.com
> Subject: Re: [dpdk-dev] [PATCH v3] app/test-crypto-perf: fix crypto
> operation resubmission
>
>
>
> > -----Original Message-----
> > From: Zhang, Roy Fan
> > Sent: Tuesday, April 18, 2017 3:49 PM
> > To: dev@dpdk.org
> > Cc: De Lara Guarch, Pablo; stable@dpdk.com
> > Subject: [PATCH v3] app/test-crypto-perf: fix crypto operation
> resubmission
> >
> > This patch fixes the crypto operation resubmission problem in crypto
> > perferformance test. Originally, when needed crypto ops amount is
> > smaller than the enqueued crypto ops in the last round, one or more
> > processed crypto operations will be re-enqueued.
> >
> > Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test
> > application")
> >
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> > Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> Applied to dpdk-next-crypto.
> Thanks,
>
> Pablo
parent reply other threads:[~2017-04-18 15:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E115CCD9D858EF4F90C690B0DCB4D8974780BD08@IRSMSX108.ger.corp.intel.com>]
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=E115CCD9D858EF4F90C690B0DCB4D8974780BD3A@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@intel.com \
--cc=stable@dpdk.org \
/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).