From: Patrick Robb <probb@iol.unh.edu>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Cody Cheng <ccheng@iol.unh.edu>, Dean Marx <dmarx@iol.unh.edu>,
Adam Hassick <ahassick@iol.unh.edu>,
Nicholas Pratte <npratte@iol.unh.edu>,
ci@dpdk.org
Subject: Intel QuickAssist crypto operations testing
Date: Tue, 8 Apr 2025 13:02:56 -0400 [thread overview]
Message-ID: <CAJvnSUC7UTYJD6jdddOV2AYxQfGsW-ZwC7FpPHJQUj+gv9rpXA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
Hi Bruce,
Do you remember last year when we had a tech board call about the server
refresh at UNH-IOL, you recommended that for the Intel processor DUT
system, we get a processor SKU which includes a QAT device? We did this,
and the SKU we selected was Intel(R) Xeon(R) Gold 5415+.
Those devices are QAT 4xxx series QAT 4942 as reported by dpdk-devbind.py
--status:
Crypto devices using kernel driver
==================================
0000:76:00.0 '4xxx Series QAT 4942' numa_node=0 drv=4xxx
unused=qat_4xxx,vfio-pci
0000:f3:00.0 '4xxx Series QAT 4942' numa_node=1 drv=4xxx
unused=qat_4xxx,vfio-pci
Cody has been setting up the testing for this QAT device, which is done via
DPDK's test-crypto-perf application. He is satisfied with the metrics the
card is getting with DPDK (he compared them against some reports Intel has
published and also what we see on a QAT PCI card on an Ampere ARM system
here at UNH).
So, he thinks we are ready to go online. However, in order to be careful,
we were wondering if we should run the information we have by an Intel
contact first. Is there any DPDK/quickassist/crypto person on your team who
could serve as a contact for this purpose? If so, I think Cody can add them
to this thread and share the more detailed info for that person for them to
approve (or disapprove).
Thanks let me know!
-Patrick
[-- Attachment #2: Type: text/html, Size: 1613 bytes --]
next reply other threads:[~2025-04-08 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 17:02 Patrick Robb [this message]
2025-04-08 18:35 ` Mcnamara, John
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=CAJvnSUC7UTYJD6jdddOV2AYxQfGsW-ZwC7FpPHJQUj+gv9rpXA@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=ahassick@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=ccheng@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=npratte@iol.unh.edu \
/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).