RE: Intel QuickAssist crypto operations testing

["Mcnamara, John" <john.mcnamara@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]

Hi,

You can bounce the numbers, or any questions, off Kai Ji (added).

John


From: Patrick Robb <probb@iol.unh.edu>
Sent: Tuesday, April 8, 2025 6:03 PM
To: Richardson, Bruce <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

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: 5792 bytes --]