DPDK patches and discussions
 help / color / mirror / Atom feed
From: "mirzaei.reza" <mirzaei.reza@ut.ac.ir>
To: dev@dpdk.org
Subject: [dpdk-dev] dpdk_21.02--kni interface does not work properly
Date: Sun, 21 Feb 2021 13:15:05 +0330
Message-ID: <82e2f6baea18519e8ee903e435c97af5@ut.ac.ir> (raw)

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: 0000:06:00.0 (socket
0)
EAL: Probe PCI driver: net_i40e (8086:158b) device: 0000: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

             reply	other threads:[~2021-02-21  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21  9:45 mirzaei.reza [this message]
2021-02-22 15:53 ` Ferruh Yigit

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=82e2f6baea18519e8ee903e435c97af5@ut.ac.ir \
    --to=mirzaei.reza@ut.ac.ir \
    --cc=dev@dpdk.org \
    /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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git