From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id CBC43E5D for ; Tue, 12 Sep 2017 16:45:26 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Sep 2017 07:45:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,383,1500966000"; d="scan'208";a="899501051" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by FMSMGA003.fm.intel.com with ESMTP; 12 Sep 2017 07:45:24 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.167]) by IRSMSX102.ger.corp.intel.com ([169.254.2.59]) with mapi id 14.03.0319.002; Tue, 12 Sep 2017 15:45:23 +0100 From: "De Lara Guarch, Pablo" To: "raghunath.borra@wipro.com" , "users@dpdk.org" Thread-Topic: Multiple cores for running Crypto and DPDK Thread-Index: AQHTKvm9H3AQmhMic02oJo6WrD3H8aKxUl0A Date: Tue, 12 Sep 2017 14:45:23 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzM4NmU2ZmQtZDc0MC00NGRkLTg4ZjAtMDFhNTQ5MWMwODRlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImpoSUhYR25kRGszQ2sxa21Ha3h5c2I2bFpqWnpYMm9yZ2FhOW9GVjJNSlU9In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] Multiple cores for running Crypto and DPDK X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Sep 2017 14:45:27 -0000 Hi Raghunath, > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of > raghunath.borra@wipro.com > Sent: Tuesday, September 12, 2017 5:44 AM > To: users@dpdk.org > Subject: [dpdk-users] Multiple cores for running Crypto and DPDK >=20 > Hi Team, >=20 > I am trying to implement Multi-core support in DPDK(16.11 version). Where > both DPDK and Crypto should run on separate logical cores. > Goal of this activity is to increase overall DPDK performance. >=20 When you say that DPDK and Crypto should run on separate cores, would you still be using cryptodev (which is part of DPDK) or a different l= ibrary? Assuming the first option, you can build a pipeline where you have a separa= te core receiving traffic, then enqueue this traffic to another core running a crypto device and then dequeue the operations with another core. > I tried to implement by initializing Crypto on separate core using > rte_eal_mp_remote_launch function. Even Crypto is running on separate > core, packets are not forwarding to that logical core for processing (But= they > are still processing on core where DPDK is running instead of crypto's co= re). >=20 > Then I found Cryptodev Scheduler support document in 17.11 > version(which is in development phase) and some part in 17.08 version. So > is it possible to do the same with 17.08 version or i have to wait till 1= 7.11 > version? Any help on this issue highly helpful and appreciated. If you have a single core processing the incoming packets, then you can use the cryptodev multi-core scheduler to use several cores performing the crypto workload on a same flow. If you have several flows, then you could initialize multiple virtual devic= es, used by multiple cores. Pablo >=20 > Thanks and Regards, > Raghunath. >=20 >=20 >=20 >=20 > The information contained in this electronic message and any attachments > to this message are intended for the exclusive use of the addressee(s) an= d > may contain proprietary, confidential or privileged information. If you a= re > not the intended recipient, you should not disseminate, distribute or cop= y > this e-mail. Please notify the sender immediately and destroy all copies = of > this message and any attachments. WARNING: Computer viruses can be > transmitted via email. The recipient should check this email and any > attachments for the presence of viruses. The company accepts no liability > for any damage caused by any virus transmitted by this email. > www.wipro.com >=20 > __________________________________________________________ > ____________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > __________________________________________________________ > ____________