- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm using DPDK23.11 and my QAT device 4942/4943 in XEON CPU
In my system, I can find PCIe devices of four 4942 devices and 16 4943 devices for each 4942 devices.
In inititializing DPDK, I added EAL parameter for QAT 4942 as like this :
"-a 0000:76:00.00,qat_dev=0" (0000:76:00.0 is pcie address for my 4942 device)
But on initializiing DPDK, it tells "cryptodev number is 0", dpdk cannot find cryptodev for QAT.
I heard that since dpdk 23.xx, QAT crypo PMD does not exist in DPDK unlike older versions, and intel maintains QAT pmd of DPDK as out-of-tree of DPDK, is it right?
How can I use QAT cryptodev PMD in DPDK23.11?
Please give me advices.
Regards,
JHwan Kim.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I setup DPDK with QAT long ago and I recall the key factor was to bind the right QAT device so it could be used by DPDK. Perhaps that's the step you are missing.
I did a quick check to the documentation for DPDK23.11 and it looks like QAT crypto PMD is still there. I'm looking at 21. Intel(R) QuickAssist (QAT) Crypto Poll Mode Driver.
DPDK has a script called dpdk-devbind.py that can show the recognized devices and which ones are using the DPDK compatible driver. Can you try running this script as follows to see what you get: # ../dpdk-devbind.py --status. You should run it from the DPDK directory in your system. Refer to the DPDK documentation is you need help running this script.
Also, if you run the command # service qat_service status, you can see all QAT devices. The ones that should be bind to DPDK are the virtual devices, not the physical ones (that is the ones labeled as "VF").
Regards,
Diego V.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I setup DPDK with QAT long ago and I recall the key factor was to bind the right QAT device so it could be used by DPDK. Perhaps that's the step you are missing.
I did a quick check to the documentation for DPDK23.11 and it looks like QAT crypto PMD is still there. I'm looking at 21. Intel(R) QuickAssist (QAT) Crypto Poll Mode Driver.
DPDK has a script called dpdk-devbind.py that can show the recognized devices and which ones are using the DPDK compatible driver. Can you try running this script as follows to see what you get: # ../dpdk-devbind.py --status. You should run it from the DPDK directory in your system. Refer to the DPDK documentation is you need help running this script.
Also, if you run the command # service qat_service status, you can see all QAT devices. The ones that should be bind to DPDK are the virtual devices, not the physical ones (that is the ones labeled as "VF").
Regards,
Diego V.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page