From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 01DBD7EE3; Thu, 17 May 2018 18:15:21 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 May 2018 09:15:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,411,1520924400"; d="scan'208";a="229378691" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by fmsmga005.fm.intel.com with ESMTP; 17 May 2018 09:15:19 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.150]) by IRSMSX102.ger.corp.intel.com ([169.254.2.83]) with mapi id 14.03.0319.002; Thu, 17 May 2018 17:15:18 +0100 From: "De Lara Guarch, Pablo" To: "Pattan, Reshma" , "Rybalchenko, Kirill" , "dev@dpdk.org" CC: "stable@dpdk.org" , "Rybalchenko, Kirill" , "Zhang, Roy Fan" Thread-Topic: [dpdk-dev] [PATCH v2] crypto/scheduler: fix multicore rings re-use Thread-Index: AQHT7dGivoHerygYPkS3HloXIMLUjaQ0F2bg Date: Thu, 17 May 2018 16:15:18 +0000 Message-ID: References: <1526280767-669-1-git-send-email-kirill.rybalchenko@intel.com> <1526480671-10763-1-git-send-email-kirill.rybalchenko@intel.com> <3AEA2BF9852C6F48A459DA490692831F2A2F1CA0@irsmsx110.ger.corp.intel.com> In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F2A2F1CA0@irsmsx110.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDU2OGI5ZDUtZDRhMC00MDhlLWEzYzgtNmM4YTkyZjg2MjI1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IkRrc3g0NHM1cm1sNTBNeDNzRUlkeGlSRk5ZbitjS0xoMjlsT1lnZjVBZ009In0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2] crypto/scheduler: fix multicore rings re-use X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 16:15:22 -0000 > -----Original Message----- > From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of Pattan, Reshma > Sent: Thursday, May 17, 2018 12:24 PM > To: Rybalchenko, Kirill ; dev@dpdk.org > Cc: stable@dpdk.org; Rybalchenko, Kirill ; = Zhang, > Roy Fan > Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] crypto/scheduler: fix mu= lticore > rings re-use >=20 > Hi, >=20 > > -----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 > > ; Zhang, Roy Fan > > > > 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 mem= ory > rings. > > > > Fixes: 4c07e0552f0a ("crypto/scheduler: add multicore scheduling > > mode") > > Cc: stable@dpdk.org > > > > v2: > > Rebase to head of dpdk-dev master branch Removed this changelog. > > > > Signed-off-by: Kirill Rybalchenko >=20 > Tested-by: Reshma Pattan Applied to dpdk-next-crypto. Thanks, Pablo