From: Nilesh Unhale <nileshunhale@cse.iitb.ac.in>
To: <users@dpdk.org>
Cc: DIPTYAROOP MAJI <diptyaroop@cse.iitb.ac.in>
Subject: [dpdk-users] Issue while running l3fwd application over DPDK 19.05
Date: Thu, 04 Jul 2019 14:37:52 +0530 [thread overview]
Message-ID: <1d5f7cca6f0561aa6870ce552be3145a@cse.iitb.ac.in> (raw)
Hello,
We tried to run l3fwd provided with DPDK using following command
sudo ./l3fwd -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)"
Following are the logs and inline comments starting from ******:
$ sudo ./l3fwd -l 1,2 -n 4 -b 01:00.0 -b 01:00.1 -- -p 0x3
--config="(0,0,1),(1,0,2)"
EAL: Detected 24 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: PCI device 0000:01:00.0 on NUMA socket 0
EAL: Device is blacklisted, not initializing
EAL: PCI device 0000:01:00.1 on NUMA socket 0
EAL: Device is blacklisted, not initializing
EAL: PCI device 0000:81:00.0 on NUMA socket 1
EAL: probe driver: 8086:1583 net_i40e
i40e_GLQF_reg_init(): i40e device 0000:81:00.0 changed global register
[0x002689a0]. original: 0x00000000, new: 0x00000029
i40e_GLQF_reg_init(): i40e device 0000:81:00.0 changed global register
[0x00268ca4]. original: 0x00001840, new: 0x00009420
EAL: PCI device 0000:81:00.1 on NUMA socket 1
EAL: probe driver: 8086:1583 net_i40e
LPM or EM none selected, default LPM on
Initializing port 0 ... Creating queues: nb_rxq=1 nb_txq=2... Port 0
modified RSS hash function based on hardware support,requested:0xa38c
configured:0x2288
Address:3C:FD:FE:9E:7B:5C, Destination:02:00:00:00:00:00, Allocated
mbuf pool on socket 0
LPM: Adding route 192.18.0.0 / 24 (0)
LPM: Adding route 192.18.1.0 / 24 (1)
LPM: Adding route 2001:200:: / 48 (0)
LPM: Adding route 2001:200:0:0:1:: / 48 (1)
txq=1,0,0 txq=2,1,0
Initializing port 1 ... Creating queues: nb_rxq=1 nb_txq=2... Port 1
modified RSS hash function based on hardware support,requested:0xa38c
configured:0x2288
Address:3C:FD:FE:9E:7B:5D, Destination:02:00:00:00:00:01, txq=1,0,0
txq=2,1,0
Initializing rx queues on lcore 1 ... rxq=0,0,0
Initializing rx queues on lcore 2 ... rxq=1,0,0
Checking link
status..........................................................................................done
Port 0 Link Down ******* ==> why is this
down and how to bring it up? ***********
Port1 Link Up. Speed 40000 Mbps -full-duplex
L3FWD: entering main loop on lcore 1
L3FWD: -- lcoreid=1 portid=0 rxqueueid=0
L3FWD: entering main loop on lcore 2
L3FWD: -- lcoreid=2 portid=1 rxqueueid=0
******* ==> it is getting stuck here, because no packets are being
received.
But, the NIC is bound to DPDK and is not showing in ifconfig. So, how
to allocate IP/ send packets to this NIC?
Do we need to add any route so that when packets come to eth iface, it
will be redirected to dpdk iface?
System specifications:
2 Machines each with ->
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
Kernel: 4.15.0-29-generic
DPDK: 19.05.0
Hardware:
CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
NIC 1: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+
(i40e)
NIC 2: Intel Corporation I350 Gigabit Network Connection (igb)
Regards,
Nilesh Unhale
reply other threads:[~2019-07-04 9:08 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=1d5f7cca6f0561aa6870ce552be3145a@cse.iitb.ac.in \
--to=nileshunhale@cse.iitb.ac.in \
--cc=diptyaroop@cse.iitb.ac.in \
--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).