From: "Zhu, Heqing" <heqing.zhu@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"'Prashant Upadhyaya'" <praupadhyaya@gmail.com>,
"'dev@dpdk.org'" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Regarding Crypto Accelerators
Date: Wed, 17 Sep 2014 15:01:49 +0000 [thread overview]
Message-ID: <CAD16F236028A64DBBC0158B1636EA4510F59BE4@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D89722616A75@IRSMSX108.ger.corp.intel.com>
8086:0435 is also valid for the new generation.
-Sent via Intel smartphone.
-----Original Message-----
From: De Lara Guarch, Pablo [pablo.de.lara.guarch@intel.com<mailto:pablo.de.lara.guarch@intel.com>]
Sent: Wednesday, September 17, 2014 04:19 AM Pacific Standard Time
To: Prashant Upadhyaya; dev@dpdk.org
Subject: Re: [dpdk-dev] Regarding Crypto Accelerators
Hi Prashant,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Prashant
> Upadhyaya
> Sent: Wednesday, September 17, 2014 7:32 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Regarding Crypto Accelerators
>
> Hi,
>
> I am planning to explore the usage of hardware crypto accelerators on Intel
> machine with Quick Assist libraries and DPDK.
> My first question is -- how do I find out whether my machine has the
> hardware crypto accelerators or not.
Use lspci to do so. Search for DH89, and if you get anything from there, that means that you have a crypto accelerator.
Anyway, if I am not wrong, the device IDs are 8086:0434 and 8086:0438 (or similar).
Regards,
Pablo
>
> Regards
> -Prashant
prev parent reply other threads:[~2014-09-17 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 6:31 Prashant Upadhyaya
2014-09-17 11:18 ` De Lara Guarch, Pablo
2014-09-17 15:01 ` Zhu, Heqing [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=CAD16F236028A64DBBC0158B1636EA4510F59BE4@SHSMSX104.ccr.corp.intel.com \
--to=heqing.zhu@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=praupadhyaya@gmail.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).