[dpdk-dev] building l2fwd-crypto example from Makefile

2021-02-07 Thread mirzaei.reza
Hello, 

I have a problem to build l2fwd-crypto example using its Makefile. I
build it using Makefile according to this [1] tutorial, when i run the
compiled file using the following command: 

./l2fwd-crypto -l 1 -n 4
--vdev="crypto_aesni_mb,socket_id=0,max_nb_sessions=128" \
-- -p 1 --cdev SW --chain CIPHER_HASH --cipher_algo "aes-cbc"
--auth_algo "sha1-hmac" 

I get the follwing error: 

EAL: Detected 16 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: FAILED TO PARSE DEVICE "CRYPTO_AESNI_GCM"
EAL: UNABLE TO PARSE DEVICE
'CRYPTO_AESNI_GCM,SOCKET_ID=0,MAX_NB_SESSIONS=128'
EAL: ERROR - EXITING WITH CODE: 1
  CAUSE: INVALID EAL ARGUMENTS 

Could anyone help me to solve this problem? 

It's worth to noting that when i build it using meson and ninja as the
following, it works successfuly. 

meson -Dexamples=l2fwd-crypto build 

Thanks in advance 

Links:
--
[1] https://doc.dpdk.org/guides-20.11/cryptodevs/aesni_gcm.html


[dpdk-dev] kni interface does not transmit anything

2021-02-12 Thread mirzaei.reza
Hello, 

I've recently migrated from dpdk-18.05 to dpdk-20.11. I built "kni"
example according to this tutorial [1], every thing is fine except that
it has no output packet (no tx). have I ignored something? I would be
grateful if anyone could help me. 

outputs: 

> ./BUILD/KNI -L 4-7 -N 4 -- -P -P 0X3 --CONFIG="(0,4,6),(1,5,7)" 




EAL: Detected 16 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.0 (socket
0)
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.1 (socket
0)
EAL: No legacy callbacks, legacy socket not created
APP: Initialising port 0 ...
APP: Initialising port 1 ... 

Checking link status
done
Port 0 Link up at 10 Gbps FDX Autoneg
Port 1 Link up at 10 Gbps FDX Autoneg
APP: 
APP: KNI Running
APP: kill -SIGUSR1 128701
APP: Show KNI Statistics.
APP: kill -SIGUSR2 128701
APP: Zero KNI Statistics.
APP: 
APP: Lcore 5 is reading from port 1
APP: Lcore 6 is writing to port 0
APP: Lcore 7 is writing to port 1
APP: Lcore 4 is reading from port 0
APP: Configure network interface of 0 up
KNI: Configure promiscuous mode of 0 to 1
KNI: Configure promiscuous mode of 0 to 0 

--


> IFCONFIG VETH0 1.1.2.39/24 UP 

> TCPDUMP -V -N -I VETH0 




07:22:26.218095 IP (tos 0x0, ttl 64, id 15551, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 1, length 64
07:22:27.218093 IP (tos 0x0, ttl 64, id 15619, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 2, length 64
07:22:28.242082 IP (tos 0x0, ttl 64, id 15826, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 3, length 64
07:22:29.266097 IP (tos 0x0, ttl 64, id 15948, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 4, length 64
07:22:30.290083 IP (tos 0x0, ttl 64, id 16060, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 5, length 64
07:22:31.314073 IP (tos 0x0, ttl 64, id 16118, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 6, length 64
07:22:32.342079 IP (tos 0x0, ttl 64, id 16236, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 7, length 64
07:22:33.366074 IP (tos 0x0, ttl 64, id 16332, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 8, length 64
07:22:34.390079 IP (tos 0x0, ttl 64, id 16511, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 9, length 64 

--


Best Regards 

 

Links:
--
[1]
https://doc.dpdk.org/guides-20.11/sample_app_ug/kernel_nic_interface.html


[dpdk-dev] kni interface does not transmit anything

2021-02-14 Thread mirzaei.reza
Hello, 

I've recently migrated from dpdk-18.05 to dpdk-20.11. I built "kni"
example according to this tutorial [1 [1]], every thing is fine except
that
it has no output packet (no tx). have I ignored something? I would be
grateful if anyone could help me. 

It may also be helpful to mention that after I change the Interface
state to UP, The output of `ip link` shows that the state of this
interface still is DOWN. 

outputs: 

> ./BUILD/KNI -L 4-7 -N 4 -- -P -P 0X3 --CONFIG="(0,4,6),(1,5,7)"


EAL: Detected 16 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.0 (socket
0)
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.1 (socket
0)
EAL: No legacy callbacks, legacy socket not created
APP: Initialising port 0 ...
APP: Initialising port 1 ... 

Checking link status
done
Port 0 Link up at 10 Gbps FDX Autoneg
Port 1 Link up at 10 Gbps FDX Autoneg
APP: 
APP: KNI Running
APP: kill -SIGUSR1 128701
APP: Show KNI Statistics.
APP: kill -SIGUSR2 128701
APP: Zero KNI Statistics.
APP: 
APP: Lcore 5 is reading from port 1
APP: Lcore 6 is writing to port 0
APP: Lcore 7 is writing to port 1
APP: Lcore 4 is reading from port 0
APP: Configure network interface of 0 up
KNI: Configure promiscuous mode of 0 to 1
KNI: Configure promiscuous mode of 0 to 0 

--


>IFCONFIG VETH0 1.1.2.39/24 UP 

>TCPDUMP -V -N -I VETH0


07:22:26.218095 IP (tos 0x0, ttl 64, id 15551, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 1, length 64
07:22:27.218093 IP (tos 0x0, ttl 64, id 15619, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 2, length 64
07:22:28.242082 IP (tos 0x0, ttl 64, id 15826, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 3, length 64
07:22:29.266097 IP (tos 0x0, ttl 64, id 15948, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 4, length 64
07:22:30.290083 IP (tos 0x0, ttl 64, id 16060, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 5, length 64
07:22:31.314073 IP (tos 0x0, ttl 64, id 16118, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 6, length 64
07:22:32.342079 IP (tos 0x0, ttl 64, id 16236, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 7, length 64
07:22:33.366074 IP (tos 0x0, ttl 64, id 16332, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 8, length 64
07:22:34.390079 IP (tos 0x0, ttl 64, id 16511, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 9, length 64 

--

Best Regards 

Links:
--
[1]
https://doc.dpdk.org/guides-20.11/sample_app_ug/kernel_nic_interface.html


Links:
--
[1]
https://doc.dpdk.org/guides-20.11/sample_app_ug/kernel_nic_interface.html


[dpdk-dev] pdump alongside the running l2fwd-crypto leads to Segmentation fault (core dumped) Error

2021-02-15 Thread mirzaei.reza
Hello, 

I setup the l2fwd-crypto example on dpdk-20.11 according to the
following topology: 

- LC-1 and LC-2 are l2fwd-crypto systems. 

- A and B are two clients. 

A <--> LC-1 <--> LC-2 <--> B 

I used the following command to config LC-1 and LC-2: 

-- 

./build/l2fwd-crypto -l 0-1 -n 4
--vdev="crypto_aesni_gcm0,socket_id=0,max_nb_sessions=128"
--vdev="crypto_aesni_gcm1,socket_id=1,max_nb_sessions=128" -- -p 0x3
--no-mac-updating --cdev SW --chain AEAD --aead_algo "aes-gcm"
--aead_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f --aead_iv
6B:8A:74:C3:D6:4A:0B:C5:F0:4B:18:6B 

--- 

I set static arp in client systems and test the topology using 'ping'
(from A to B). Everything works fine. 

But, using pdump on LC-1 while ping is running, leads to Segmentation
fault (core dumped). 

 

./dpdk-pdump -- --pdump 'port=0,queue=*,rx-dev=/tmp/rx.pcap' 

 

OUTPUTS: 

DPDK-PDUMP 

-- 

EAL: Detected 16 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket
/var/run/dpdk/rte/mp_socket_372404_1811cd7dfadb50
EAL: Selected IOVA mode 'PA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.0 (socket
0)
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.1 (socket
0)
CRYPTODEV: Creating cryptodev crypto_aesni_gcm0 

CRYPTODEV: Initialisation parameters - name: crypto_aesni_gcm0,socket
id: 0, max queue pairs: 8
CRYPTODEV: Creating cryptodev crypto_aesni_gcm1 

CRYPTODEV: Initialisation parameters - name: crypto_aesni_gcm1,socket
id: 0, max queue pairs: 8
Port 2 MAC: 02 70 63 61 70 00
core (0), capture for (1) tuples
- port 0 device ((null)) queue 65535
PRIMARY PROCESS IS NO LONGER ACTIVE, EXITING...
EAL: FAILED TO SEND TO (/VAR/RUN/DPDK/RTE/MP_SOCKET) DUE TO CONNECTION
REFUSED
EAL: FAIL TO SEND REQUEST /VAR/RUN/DPDK/RTE/MP_SOCKET:MP_PDUMP
PDUMP_PREPARE_CLIENT_REQUEST(): CLIENT REQUEST FOR PDUMP ENABLE/DISABLE
FAILED
EAL: FAILED TO SEND TO (/VAR/RUN/DPDK/RTE/MP_SOCKET) DUE TO CONNECTION
REFUSED
EAL: FAIL TO SEND REQUEST /VAR/RUN/DPDK/RTE/MP_SOCKET:EAL_DEV_MP_REQUEST
EAL: CANNOT SEND REQUEST TO PRIMARY
EAL: FAILED TO SEND HOTPLUG REQUEST TO PRIMARY
# PDUMP DEBUG STATS #
 -PACKETS DEQUEUED: 1
 -PACKETS TRANSMITTED TO VDEV: 1
 -PACKETS FREED: 0 

-


L2FWD-CRYPTO 

-


EAL: Detected 16 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.0 (socket
0)
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.1 (socket
0)
CRYPTODEV: Creating cryptodev crypto_aesni_gcm0 

CRYPTODEV: Initialisation parameters - name: crypto_aesni_gcm0,socket
id: 0, max queue pairs: 8
CRYPTODEV: Creating cryptodev crypto_aesni_gcm1 

CRYPTODEV: Initialisation parameters - name: crypto_aesni_gcm1,socket
id: 0, max queue pairs: 8
EAL: No legacy callbacks, legacy socket not created
MAC updating disabled
Initializing port 0... Port 0, MAC address: 40:A6:B7:1E:9D:44 

Initializing port 1... Port 1, MAC address: 40:A6:B7:1E:9D:45 

Checking link statusdone
Port 0 Link up at 10 Gbps FDX Autoneg
Port 1 Link up at 10 Gbps FDX Autoneg
Lcore 0: RX port 0
Lcore 1: RX port 1
Allocated pool "priv_sess_mp_0" on socket 0
CRYPTODEV: elt_size 0 is expanded to 320 

Allocated pool "sess_mp_0" on socket 0
Lcore 0: cryptodev 0
Lcore 1: cryptodev 1
L2FWD: entering main loop on lcore 1
L2FWD: -- lcoreid=1 portid=1
L2FWD: entering main loop on lcore 0
L2FWD: -- lcoreid=0 portid=0
L2FWD: -- lcoreid=0 cryptoid=0
Options:-
nportmask: 3
ports per lcore: 1
refresh period : 1
single lcore mode: disabled
stats_printing: enabled
sessionless crypto: disabled 

Crypto chain: Input --> Authenticated encryption --> Output
L2FWD: -- lcoreid=1 cryptoid=1 

 AEAD information ---
Algorithm: aes-gcm
AEAD key: at [0x7fff90cc8a58], len=16
Options:-
nportmask: 3
ports per lcore: 1
refresh period : 1
single lcore mode: disabled
stats_printing: enabled
sessionless crypto: disabled 

Crypto chain: Input --> Authenticated encryption --> Output 

 AEAD information ---
Algorithm: aes-gcm
AEAD key: at [0x7fff90cc8a58], len=16
: 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F |

IV: at [0x1004330c0], len=12
: 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F |

IV: at [0x1004330c0], len=1

[dpdk-dev] dpdk_21.02--kni interface does not work properly

2021-02-21 Thread mirzaei.reza
Hello, 

I've recently migrated from dpdk-18.05 to dpdk-21.02. I built "kni"
example according to this tutorial [1 [1]], every thing is fine except
that
it has no output packet (no tx). There is a same problem in dpdk-20.11.
Have I ignored something? I would be
grateful if anyone could help me. 

It may also be helpful to mention that after I change the Interface
state to UP, The output of `ip link` shows that the state of this
interface still is DOWN. 

outputs: 

> ./BUILD/KNI -L 4-7 -N 4 -- -P -P 0X3 --CONFIG="(0,4,6),(1,5,7)"


EAL: Detected 16 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.0 (socket
0)
EAL: Probe PCI driver: net_i40e (8086:158b) device: :06:00.1 (socket
0)
EAL: No legacy callbacks, legacy socket not created
APP: Initialising port 0 ...
APP: Initialising port 1 ...

Checking link status
done
Port 0 Link up at 10 Gbps FDX Autoneg
Port 1 Link up at 10 Gbps FDX Autoneg
APP: 
APP: KNI Running
APP: kill -SIGUSR1 128701
APP: Show KNI Statistics.
APP: kill -SIGUSR2 128701
APP: Zero KNI Statistics.
APP: 
APP: Lcore 5 is reading from port 1
APP: Lcore 6 is writing to port 0
APP: Lcore 7 is writing to port 1
APP: Lcore 4 is reading from port 0
APP: Configure network interface of 0 up
KNI: Configure promiscuous mode of 0 to 1
KNI: Configure promiscuous mode of 0 to 0

--


>IFCONFIG VETH0 1.1.2.39/24 UP 

>TCPDUMP -V -N -I VETH0


07:22:26.218095 IP (tos 0x0, ttl 64, id 15551, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 1, length 64
07:22:27.218093 IP (tos 0x0, ttl 64, id 15619, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 2, length 64
07:22:28.242082 IP (tos 0x0, ttl 64, id 15826, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 3, length 64
07:22:29.266097 IP (tos 0x0, ttl 64, id 15948, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 4, length 64
07:22:30.290083 IP (tos 0x0, ttl 64, id 16060, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 5, length 64
07:22:31.314073 IP (tos 0x0, ttl 64, id 16118, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 6, length 64
07:22:32.342079 IP (tos 0x0, ttl 64, id 16236, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 7, length 64
07:22:33.366074 IP (tos 0x0, ttl 64, id 16332, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 8, length 64
07:22:34.390079 IP (tos 0x0, ttl 64, id 16511, offset 0, flags [DF],
proto ICMP (1), length 84)
1.1.2.2 > 1.1.2.39: ICMP echo request, id 229, seq 9, length 64

--

Best Regards

Links:
--
[1]
https://doc.dpdk.org/guides-21.02/sample_app_ug/kernel_nic_interface.html
[1] 

Links:
--
[1]
https://doc.dpdk.org/guides-20.11/sample_app_ug/kernel_nic_interface.html