From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/crypto-perf: fix mempool create call failure
Date: Mon, 16 Jul 2018 14:13:41 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8FBB8B@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <d3eaa5aa-c79f-27c7-ce36-0f5f2317893f@nxp.com>
> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Monday, July 16, 2018 12:40 PM
> To: Nicolau, Radu <radu.nicolau@intel.com>; dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] app/crypto-perf: fix mempool create call failure
>
> On 7/16/2018 4:44 PM, Radu Nicolau wrote:
>
> > Using a small number of sessions results in rte_mempool_create call
> > with cache_size > n, which fails. There is no need to cache the
> > elements, as there is no performance impact.
> >
> > Fixes: 501c0a3b14c3 ("app/crypto-perf: limit number of sessions")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> > ---
>
> This patch should not be for stable. As the patch which introduced this issue is
> still not released.
>
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
>
Applied to dpdk-next-crypto, removing the Cc stable line.
Thanks,
Pablo
prev parent reply other threads:[~2018-07-16 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 11:14 Radu Nicolau
2018-07-16 11:39 ` Akhil Goyal
2018-07-16 14:13 ` 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=E115CCD9D858EF4F90C690B0DCB4D8977F8FBB8B@IRSMSX107.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=radu.nicolau@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).