[dpdk-dev] [PATCH] assign QAT cryptodev to correct NUMA node

De Lara Guarch, Pablo pablo.de.lara.guarch at intel.com
Mon Mar 26 11:03:43 CEST 2018



> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Trahe, Fiona
> Sent: Friday, March 9, 2018 6:18 PM
> To: Lee Roberts <lee.roberts at hpe.com>; Griffin, John
> <john.griffin at intel.com>; Jain, Deepak K <deepak.k.jain at intel.com>
> Cc: dev at dpdk.org; Trahe, Fiona <fiona.trahe at intel.com>
> Subject: Re: [dpdk-dev] [PATCH] assign QAT cryptodev to correct NUMA
> node
> 
> Hi Lee,
> Thanks for investigating this.
> 
> > -----Original Message-----
> > From: Lee Roberts [mailto:lee.roberts at hpe.com]
> > Sent: Friday, March 9, 2018 6:01 PM
> > To: Griffin, John <john.griffin at intel.com>; Trahe, Fiona
> > <fiona.trahe at intel.com>; Jain, Deepak K <deepak.k.jain at intel.com>
> > Cc: dev at dpdk.org; Lee Roberts <lee.roberts at hpe.com>
> > Subject: [PATCH] assign QAT cryptodev to correct NUMA node
> >
> > rte_cryptodev_pmd_init_params should use NUMA node of the QAT
> device
> > for its socket_id rather than the socket_id of the initializing process.
> >
> > Signed-off-by: Lee Roberts <lee.roberts at hpe.com>
> Acked-by: Fiona Trahe <fiona.trahe at intel.com>

Modified title to "crypto/qat: assign device to correct NUMA node"

Applied to dpdk-next-crypto.
Thanks,

Pablo



More information about the dev mailing list