From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 7E0198019; Thu, 17 May 2018 18:15:15 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 May 2018 09:15:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,411,1520924400"; d="scan'208";a="225076535" Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59]) by orsmga005.jf.intel.com with ESMTP; 17 May 2018 09:15:12 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.150]) by IRSMSX151.ger.corp.intel.com ([169.254.4.167]) with mapi id 14.03.0319.002; Thu, 17 May 2018 17:15:11 +0100 From: "De Lara Guarch, Pablo" To: "De Lara Guarch, Pablo" , "Zhang, Roy Fan" , "dev@dpdk.org" CC: "Rybalchenko, Kirill" , "stable@dpdk.org" Thread-Topic: [dpdk-stable] [PATCH v2] crypto/scheduler: fix possible duplicated ring names Thread-Index: AQHT7R2yGNerB5hMjECAHUoNsGJLSaQ0GBsw Date: Thu, 17 May 2018 16:15:10 +0000 Message-ID: References: <20180516131032.77082-1-roy.fan.zhang@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOWU4OWY3ZDQtOGI1Ny00ODlkLTg1YTAtYjlmNDUyZjE4MmNiIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImV1OU5DQXlqUEloOVIycEdocjBSU3hPOHJ6RUh3SitmazJyODFJaUZCWFE9In0= 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] [dpdk-stable] [PATCH v2] crypto/scheduler: fix possible duplicated ring names 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:17 -0000 > -----Original Message----- > From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of De Lara Guarch= , > Pablo > Sent: Wednesday, May 16, 2018 2:56 PM > To: Zhang, Roy Fan ; dev@dpdk.org > Cc: Rybalchenko, Kirill ; stable@dpdk.org > Subject: Re: [dpdk-stable] [PATCH v2] crypto/scheduler: fix possible dupl= icated > ring names >=20 >=20 >=20 > > -----Original Message----- > > From: Zhang, Roy Fan > > Sent: Wednesday, May 16, 2018 2:11 PM > > To: dev@dpdk.org > > Cc: Zhang, Roy Fan ; Rybalchenko, Kirill > > ; stable@dpdk.org; De Lara Guarch, Pablo > > > > Subject: [PATCH v2] crypto/scheduler: fix possible duplicated ring > > names > > > > This patch fixes the possible duplicated ring names in multi-core sched= uler. > > Originally two or more multi-core schedulers may have same worker ring > > names thus will cause initialization error. > > > > Fixes: 4c07e0552f0a ("crypto/scheduler: add multicore scheduling > > mode") Added Cc: stable@dpdk.org > > > > Signed-off-by: Fan Zhang >=20 > Acked-by: Pablo de Lara Applied to dpdk-next-crypto. Thanks, Pablo