Re: [dpdk-users] Multiple cores for running Crypto and DPDK

["De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>]

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
> 
> Hi Team,
> 
> 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.
> 

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 library?
Assuming the first option, you can build a pipeline where you have a separate
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 core).
> 
> 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 17.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 devices,
used by multiple cores.

Pablo


> 
> Thanks and Regards,
> Raghunath.
> 
> 
> 
> 
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> 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
> 
> __________________________________________________________
> ____________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> __________________________________________________________
> ____________