From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "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] crypto/scheduler: fix queue pair configuration
Date: Mon, 17 Apr 2017 21:43:21 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8974780B56C@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1491836454-124949-1-git-send-email-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Monday, April 17, 2017 9:32 PM
> To: Zhang, Roy Fan; dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: RE: [PATCH] crypto/scheduler: fix queue pair configuration
>
>
>
> > -----Original Message-----
> > From: Zhang, Roy Fan
> > Sent: Monday, April 10, 2017 4:01 PM
> > To: dev@dpdk.org
> > Cc: De Lara Guarch, Pablo; stable@dpdk.org
> > Subject: [PATCH] crypto/scheduler: fix queue pair configuration
> >
> > This patch fixes the queue pair configuration for the scheduler PMD.
> > The queue pairs of a scheduler may have different nb_descriptors sizes,
> > which was not the case. Also, the maximum available objects in a
> > queue pair is 1 object smaller than nb_descriptors. This patch fixes
> > these issues.
> >
> > Fixes: 4987bbaa4810 ("crypto/scheduler: add packet size based mode")
> >
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Wrong fixes line -> Changed to "a783aa634410 ("crypto/scheduler: add packet size based mode")".
Also, this patch doesn't need to go to stable tree, as it is fixing a commit
that was sent in this release.
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-04-17 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 15:00 Fan Zhang
2017-04-17 20:31 ` De Lara Guarch, Pablo
2017-04-17 21:43 ` De Lara Guarch, Pablo [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8974780B56C@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).