From: Gennady Abramov <agv100@gmail.com>
To: users@dpdk.org
Subject: 22.11: cannot see packets on NXP LX2160a board
Date: Wed, 18 Jan 2023 22:50:23 +0300 [thread overview]
Message-ID: <CAKXMf0gPjheyBbiaCpUiFCYG1wp3vqVWdL8ZjDHmoh_kqqGWbw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4456 bytes --]
Hello,
I'm trying to use 22.11 DPDK on SolidRun HoneyComb/ NXP LX2160a board,
with DPAA2 interfaces. 22.11 is attractive as dpaa pmd was seriously
updated in it.
DPAA2 interfaces are seen by testpmd, but the problem is, neither testpmd,
neither application I use (vpp) cannot see a packet either tx on rx. In
example below, it should see lots of garbage (such as BUM from network
ports connected to).
Ports were also returned to Linux kernel and tcpdump sees lots of incoming.
Ports were tested with older DPDK versions and also sees incoming packets.
For unknown reason, this one shows all-zeroes.
Any ideas what is wrong with configuration ?
root@localhost:~# restool -m
MC firmware version: 10.32.0
root@localhost:~# numactl -H
available: 1 nodes (0)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
node 0 size: 13886 MB
node 0 free: 8440 MB
node distances:
node 0
0: 10
root@localhost:~# numactl -s
policy: default
preferred node: current
physcpubind: 0 1 2 3 4 5 6 7
cpubind: 0
nodebind: 0
membind: 0
root@localhost:~# numactl -H
available: 1 nodes (0)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
node 0 size: 13886 MB
node 0 free: 8440 MB
node distances:
node 0
0: 10
/dpdk-testpmd
EAL: Detected CPU lcores: 16
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
fslmc: Skipping invalid device (power)
EAL: Selected IOVA mode 'PA'
EAL: 1440 hugepages of size 2097152 reserved, but no mounted hugetlbfs
found for that size
EAL: VFIO support initialized
PMD: dpni.2: netdev created, connected to dpmac.7
PMD: dpni.3: netdev created, connected to dpmac.8
PMD: dpni.4: netdev created, connected to dpmac.10
TELEMETRY: No legacy callbacks, legacy socket not created
testpmd: create a new mbuf pool <mb_pool_0>: n=203456, size=2176, socket=0
testpmd: preferred mempool ops selected: dpaa2
Warning! port-topology=paired and odd forward ports number, the last port
will pair with itself.
Configuring Port 0 (socket 0)
Port 0: D0:63:B4:03:1C:CA
Configuring Port 1 (socket 0)
Port 1: D0:63:B4:03:1C:CB
Configuring Port 2 (socket 0)
Port 2: D0:63:B4:03:1C:CD
Checking link statuses...
Port 0: link state change event
Port 1: link state change event
Port 2: link state change event
Done
No commandline core given, start packet forwarding
io packet forwarding - ports=3 - cores=1 - streams=3 - NUMA support
enabled, MP allocation mode: native
Logical Core 1 (socket 0) forwards packets on 3 streams:
RX P=0/Q=0 (socket 0) -> TX P=1/Q=0 (socket 0) peer=02:00:00:00:00:01
RX P=1/Q=0 (socket 0) -> TX P=0/Q=0 (socket 0) peer=02:00:00:00:00:00
RX P=2/Q=0 (socket 0) -> TX P=2/Q=0 (socket 0) peer=02:00:00:00:00:02
io packet forwarding packets/burst=32
nb forwarding cores=1 - nb forwarding ports=3
port 0: RX queue number: 1 Tx queue number: 1
Rx offloads=0x0 Tx offloads=0x10000
RX queue: 0
RX desc=512 - RX free threshold=1
RX threshold registers: pthresh=0 hthresh=0 wthresh=0
RX Offloads=0x0
TX queue: 0
TX desc=512 - TX free threshold=0
TX threshold registers: pthresh=0 hthresh=0 wthresh=0
TX offloads=0x0 - TX RS bit threshold=0
port 1: RX queue number: 1 Tx queue number: 1
Rx offloads=0x0 Tx offloads=0x10000
RX queue: 0
RX desc=512 - RX free threshold=1
RX threshold registers: pthresh=0 hthresh=0 wthresh=0
RX Offloads=0x0
TX queue: 0
TX desc=512 - TX free threshold=0
TX threshold registers: pthresh=0 hthresh=0 wthresh=0
TX offloads=0x0 - TX RS bit threshold=0
port 2: RX queue number: 1 Tx queue number: 1
Rx offloads=0x0 Tx offloads=0x10000
RX queue: 0
RX desc=512 - RX free threshold=1
RX threshold registers: pthresh=0 hthresh=0 wthresh=0
RX Offloads=0x0
TX queue: 0
TX desc=512 - TX free threshold=0
TX threshold registers: pthresh=0 hthresh=0 wthresh=0
TX offloads=0x0 - TX RS bit threshold=0
Press enter to exit
Telling cores to stop...
Waiting for lcores to finish...
---------------------- Forward statistics for port 0
----------------------
RX-packets: 0 RX-dropped: 0 RX-total: 0
TX-packets: 0 TX-dropped: 0 TX-total: 0
----------------------------------------------------------------------------
...
Done.
Stopping port 0...
Stopping ports...
dpaa2_net: dpni disable failed (-110)
Done
--
Regards,
Gennady Abramov
[-- Attachment #2: Type: text/html, Size: 5250 bytes --]
reply other threads:[~2023-01-18 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAKXMf0gPjheyBbiaCpUiFCYG1wp3vqVWdL8ZjDHmoh_kqqGWbw@mail.gmail.com \
--to=agv100@gmail.com \
--cc=users@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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).