From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Rybalchenko, Kirill" <kirill.rybalchenko@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Rybalchenko, Kirill" <kirill.rybalchenko@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] crypto/scheduler: fix multicore rings re-use
Date: Thu, 17 May 2018 11:24:12 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A2F1CA0@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <1526480671-10763-1-git-send-email-kirill.rybalchenko@intel.com>
Hi,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kirill Rybalchenko
> Sent: Wednesday, May 16, 2018 3:25 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Rybalchenko, Kirill <kirill.rybalchenko@intel.com>;
> Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Subject: [dpdk-dev] [PATCH v2] crypto/scheduler: fix multicore rings re-use
>
> When scheduler mode changed from multicore to roundrobin and back to
> multicore, scheduler tries to create memory rings with the same name and
> fails. The fix allows to lookup and re-use previously allocated memory rings.
>
> Fixes: 4c07e0552f0a ("crypto/scheduler: add multicore scheduling mode")
> Cc: stable@dpdk.org
>
> v2:
> Rebase to head of dpdk-dev master branch
>
> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
Tested-by: Reshma Pattan <reshma.pattan@intel.com>
next prev parent reply other threads:[~2018-05-17 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 6:52 [dpdk-stable] [PATCH] " Kirill Rybalchenko
2018-05-14 10:01 ` Zhang, Roy Fan
2018-05-16 8:44 ` De Lara Guarch, Pablo
2018-05-16 12:57 ` [dpdk-stable] [dpdk-dev] " Pattan, Reshma
2018-05-16 14:24 ` [dpdk-stable] [PATCH v2] " Kirill Rybalchenko
2018-05-16 15:43 ` De Lara Guarch, Pablo
2018-05-17 11:24 ` Pattan, Reshma [this message]
2018-05-17 16:15 ` [dpdk-stable] [dpdk-dev] " 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=3AEA2BF9852C6F48A459DA490692831F2A2F1CA0@irsmsx110.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=dev@dpdk.org \
--cc=kirill.rybalchenko@intel.com \
--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).