From: David Aldrich <David.Aldrich@EMEA.NEC.COM>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Newbie: Help requested to get l2fwd example working
Date: Fri, 13 Jan 2017 08:12:11 +0000 [thread overview]
Message-ID: <74d60b2109824fcdad5dbef5a04b27d3@EUX13SRV1.EU.NEC.COM> (raw)
Hi
To get familiar with DPDK, I am running the l2fwd example on a PC running Wind River Linux and fitted with an HP 560SFP+ 2-port NIC. I enable one port for l2fwd and send UDP packets to it from another PC. The problem is that the l2fwd example does not report these packets in its statistics - it reports 0 packets received. I would like some advice on how to debug this please.
Here's some more information:
I have a bash script that initialises the dpdk environment and calls dpdk_nic_bind.py. The output looks ok and is shown at the end of this email.
I run l2fwd as follows:
build/l2fwd -c f -n2 -- -q 1 -p 2
This runs the example on 2 lcores, 1 port (the second one) and 1 rx queue per lcore.
On the sending PC I have added an arp entry for the remote port and, using Wireshark, I can see that the UDP packet is sent with the correct MAC address.
So all seems set up ok, but l2fwd does not see a packet. Please can someone help me with this?
Best regards
David
Output of bash script
=================
# ./leda_dpdk_setup.sh
Using directory: /root/dpdk-2.2.0/x86_64-native-linuxapp-gcc
HugePages_Total: 28
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 1048576 kB
trying to remove old igb_uio module and may get an error message, ignore it trying to remove old rte_kni module and may get an error message, ignore it
Network devices using DPDK-compatible driver ============================================
0000:04:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=windrvr1221
0000:04:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=windrvr1221
Network devices using kernel driver
===================================
0000:09:00.0 'I210 Gigabit Network Connection' if=eth0 drv=igb unused=windrvr1221,igb_uio
0000:0a:00.0 'I210 Gigabit Network Connection' if=eth1 drv=igb unused=windrvr1221,igb_uio *Active*
Other network devices
=====================
<none>
Command 'lspci | grep Ether' output for reference
04:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
04:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
09:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
0a:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) root@localhost:~#
next reply other threads:[~2017-01-13 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 8:12 David Aldrich [this message]
2017-01-13 11:01 ` Marco Kwok
2017-01-13 11:12 ` David Aldrich
2017-01-13 11:24 ` Marco Kwok
2017-01-15 19:01 ` David Aldrich
2017-01-16 3:12 ` zhilong zheng
2017-01-16 11:34 ` David Aldrich
2017-01-16 13:37 ` zhilong zheng
2017-01-16 13:41 ` David Aldrich
2017-01-16 13:48 ` zhilong zheng
2017-01-16 17:55 ` David Aldrich
2017-01-19 9:05 ` David Aldrich
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=74d60b2109824fcdad5dbef5a04b27d3@EUX13SRV1.EU.NEC.COM \
--to=david.aldrich@emea.nec.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).