2219351_en-US

[#1]

Enable Hardware Crypto Engine

Hello sir, 

Currently I am using NXP Layerscape 1046ARDB kit in which I am executing L2fwd-crypto code with the software crypto-device as INntel IPsec-mb. Also TLS is  running parallely to it for key exchange 

Now I want to migrate my code to kit with an objective to use Hardware crypto engine. So following are my queries related to it.

Q1) How can I enable the hardware crypto engine in the kit.

I'm currently giving command as:

meson setup build --crossfile config/arm/arm64 -dpaa-linux_gcc -Denabledrivers=bus/dpaa,mempool/dpaa,crypto/dpaa_sec

But only in Drivers section dma,raw,crypto dpaa is coming but not in enabled drivers section.

How to resolve it?

Q2) In the earlier version of the DPDK KNI was provided that is not available in newer version. So what is the alternative provided for this?

Re: Enable Hardware Crypto Engine

Hello,

I have enabled CAAM in my kernel module now. Now the problem I am encountering is : 

Q1)

(Last lines of the output dmesg | grep -i caam )

Device caam-keygen registered 

caam_jr 17300000.jr : failed to flush job ring 2.

probe of 17300000.jr failed with error -5.                                                                                                                                                                         

Q2) 

for af-xdp the traffic coming on port eno1 is handled like this 

sudo ethtool -L eno1 combined 2

# Add a flow rule to direct TCP traffic destined for port 443 to RX queue 1
sudo ethtool -N eno1 flow-type tcp4 dst-port 443 action 1

                                                                                                                                                                        ./dpdk_app ... --vdev="net_af_xdp0,iface=eno1,start_queue=1,queue_count=1" ...

nb_rx = rte_eth_rx_burst(portid, 0, pkts_burst, MAX_PKT_BURST);

Here I am giving that specific portid on which data is coming.

Please calrify the queries.                                                                                                                                                                                  

Re: Enable Hardware Crypto Engine

Hello,

Q1) To enable the hardware crypto engine:
The issue appears to be with your meson build command. For DPAA crypto acceleration support in DPDK, you need to properly include the DPAA Security driver. Check if you have the required dependencies installed and the correct Linux headers. The syntax in your command looks correct, but you may need to ensure your build environment has all necessary prerequisites.

Try adding the full path to the DPAA SEC driver in your command:
```
meson setup build --crossfile config/arm/arm64_dpaa_linux_gcc -Denable_drivers=bus/dpaa,mempool/dpaa,crypto/dpaa_sec
```

If you still don't see it in the enabled drivers section, verify the DPAA crypto accelerator is properly initialized in your kernel and that the required DPDK libraries are properly installed.

Q2) Regarding KNI (Kernel NIC Interface) alternatives:
In newer DPDK versions, KNI has been deprecated and removed. The recommended alternatives are:

1. AF_XDP (Address Family eXpress Data Path) - Provides a high-performance packet processing interface
2. AF_PACKET - A standard socket interface for packet processing
3. Virtio-user - For userspace networking applications

For your specific use case with TLS key exchange running in parallel with L2fwd-crypto, AF_XDP would likely provide the best performance characteristics as a KNI replacement.

Regards