From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
Lee Roberts <lee.roberts@hpe.com>,
"Griffin, John" <john.griffin@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] assign QAT cryptodev to correct NUMA node
Date: Mon, 26 Mar 2018 09:03:43 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CCBD333@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B4358933BCD9@IRSMSX103.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Trahe, Fiona
> Sent: Friday, March 9, 2018 6:18 PM
> To: Lee Roberts <lee.roberts@hpe.com>; Griffin, John
> <john.griffin@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>
> Cc: dev@dpdk.org; Trahe, Fiona <fiona.trahe@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@hpe.com]
> > Sent: Friday, March 9, 2018 6:01 PM
> > To: Griffin, John <john.griffin@intel.com>; Trahe, Fiona
> > <fiona.trahe@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>
> > Cc: dev@dpdk.org; Lee Roberts <lee.roberts@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@hpe.com>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
Modified title to "crypto/qat: assign device to correct NUMA node"
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2018-03-26 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 18:00 Lee Roberts
2018-03-09 18:17 ` Trahe, Fiona
2018-03-26 9:03 ` De Lara Guarch, Pablo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E115CCD9D858EF4F90C690B0DCB4D8976CCBD333@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@intel.com \
--cc=lee.roberts@hpe.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).