From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] app/crypto-perf: fix invalid latency for QAT PMD
Date: Thu, 9 Mar 2017 21:45:48 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476EC0A5@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D897476EC068@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Thursday, March 09, 2017 9:25 PM
> To: De Lara Guarch, Pablo; Mrozowicz, SlawomirX; Doherty, Declan
> Cc: dev@dpdk.org; Mrozowicz, SlawomirX
> Subject: RE: [dpdk-dev] [PATCH] app/crypto-perf: fix invalid latency for QAT
> PMD
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch,
> > Pablo
> > Sent: Monday, March 06, 2017 4:29 PM
> > To: Mrozowicz, SlawomirX; Doherty, Declan
> > Cc: dev@dpdk.org; Mrozowicz, SlawomirX
> > Subject: Re: [dpdk-dev] [PATCH] app/crypto-perf: fix invalid latency for
> QAT
> > PMD
> >
> >
> >
> > > -----Original Message-----
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Slawomir
> > > Mrozowicz
> > > Sent: Thursday, February 16, 2017 3:51 PM
> > > To: Doherty, Declan
> > > Cc: dev@dpdk.org; Mrozowicz, SlawomirX
> > > Subject: [dpdk-dev] [PATCH] app/crypto-perf: fix invalid latency for QAT
> > > PMD
> > >
> > > Fixes invalid latency result when using the performance application and
> > > hardware QAT PMD. It occurred when the number of processed packets
> > was
> > > higher then the size of the internal QAT PMD ring buffer and the buffer
> > > was overflowed.
> > > Fixed by correcting the registration of the enqueued packets and freeing
> > > memory space for not enqueued packets.
> > >
> > > Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test
> > > application")
> > >
> > > Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> >
> > Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> Applied to dpdk-next-crypto.
> Thanks,
>
> Pablo
CC'ing stable list.
parent reply other threads:[~2017-03-09 21:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E115CCD9D858EF4F90C690B0DCB4D897476EC068@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=E115CCD9D858EF4F90C690B0DCB4D897476EC0A5@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=slawomirx.mrozowicz@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).