I am running as root, yes.
I had cut out some other printouts, so I’ll include them here in case they
matter.
EAL: Detected 28 lcore(s)
EAL: Probing VFIO support...
EAL: PCI device 0000:0b:00.0 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:0b:00.1 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:0d:00.0 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:0d:00.1 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:81:00.0 on NUMA socket 1
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:81:00.1 on NUMA socket 1
EAL: probe driver: 8086:1521 net_e1000_igb
Found NIC(0):
Device Address:
dpdk-lcore: 1
dpdk-ipv4: 192.168.30.1/24
dpdk-num-desc: 4096
dpdk-io-cpu: 1
dpdk-mac: aa:bb:cc:dd:ee:f4
Found NIC(1):
Device Address:
dpdk-lcore: 2
dpdk-ipv4: 192.168.40.1/24
dpdk-io-cpu: 2
dpdk-num-desc: 4096
dpdk-mac: aa:bb:cc:dd:ee:f5
MD: ixgbe_dev_link_status_print(): Port 0: Link Up - speed 0 Mbps - half-duplex
EAL: Port 0 MAC: aa bb cc dd ee f4
PMD: ixgbe_dev_link_status_print(): Port 1: Link Up - speed 0 Mbps - half-duplex
EAL: Port 1 MAC: aa bb cc dd ee f5
EAL: Waiting for links to come up...
EAL: Port 0 UP: 1, 10000 Mbps
EAL: Port 1 UP: 1, 10000 Mbps
EAL: Init DONE!
EAL: Starting I/O threads!
USER2: Thread 1 started
USER2: Thread 2 started
Addr 192.168.30.2, port 49152
[INFO] [X300] X300 initialization sequence...
From: Marcus D Leech <[email protected]>
Sent: Friday, July 24, 2020 3:14 PM
To: Carmichael, Ryan <[email protected]>
Cc: [email protected]
Subject: [EXTERNAL] Re: [USRP-users] Getting DPDK to work
You’re running that as root, correct?
Sent from my iPhone
On Jul 24, 2020, at 4:10 PM, Carmichael, Ryan
<[email protected]<mailto:[email protected]>> wrote:
So now I’m so close to working with DPDK, seemingly. Every time I fix one thing
there’s another.
./rx_samples_to_file --args="use_dpdk=1,addr=192.168.30.2,addr2=192.168.40.2"
--duration 0.01
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
[INFO] [X300] Radio 1x clock: 200 MHz
[INFO] [X300] Radio 1x clock: 200 MHz
[INFO] [2/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D00000000000)
[INFO] [2/DmaFIFO_0] BIST passed (Throughput: 1311 MB/s)
[INFO] [2/DmaFIFO_0] BIST passed (Throughput: 1302 MB/s)
.
.
.
[INFO] [2/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000)
INFO] [2/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000)
terminate called after throwing an instance of 'uhd::io_error'
what(): EnvironmentError: IOError: Block ctrl (CE_00_Port_30) no response
packet - AssertionError: bool(buff)
in uint64_t ctrl_iface_impl<_endianness>::wait_for_ack(bool, double) [with
uhd::endianness_t _endianness = (uhd::endianness_t)0; uint64_t = long unsigned
int]
at /home/ryan/gitlab/uhd/host/lib/rfnoc/ctrl_iface.cpp:151
Just searching online it seemed like most people recommended reflashing the
fpga, which I did. No change.
From: USRP-users
<[email protected]<mailto:[email protected]>>
On Behalf Of Carmichael, Ryan via USRP-users
Sent: Friday, July 24, 2020 12:39 PM
To: [email protected]<mailto:[email protected]>
Subject: [EXTERNAL] Re: [USRP-users] Getting DPDK to work
FYI the problem ended up being that the UHD configuration file requires an
underscore with [use_dpdk=1] (instead of a dash, like everything else in the
file uses), and also that dpdk-io-cpu=x is required instead of dpdk-lcore to
initialize the adapters. Thanks for the help.
Of course now rx_samples_to_file segfaults in rte_eth_rx_queue_setup, but at
least it’s forward movement.
- Ryan
From: USRP-users
<[email protected]<mailto:[email protected]>>
On Behalf Of Marcus D. Leech via USRP-users
Sent: Friday, July 24, 2020 9:18 AM
To: [email protected]<mailto:[email protected]>
Subject: [EXTERNAL] Re: [USRP-users] Getting DPDK to work
On 07/24/2020 09:44 AM, Carmichael, Ryan via USRP-users wrote:
I’ve got an X310, UHD 3.15.LTS (compiled with DPDK support), DPDK 17.11 on Red
Hat. I feel like things are 95% of the way there, but I can’t get UHD to work
with DPDK.
Long story short, I’m getting the error “EAL: Please set IPv4 address for port
0 before opening socket”. I wonder if it’s not reading my uhd conf file.
Before dpdk-devbind, the X310 has two IP addresses that are pingable
(192.168.30.2 and 40.2) from my NICs:
enp13s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 192.168.30.99 netmask 255.255.255.0 broadcast 192.168.30.255
ether aa:bb:cc:dd:ee:01 txqueuelen 1000 (Ethernet)
enp13s0f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 9001
inet 192.168.40.99 netmask 255.255.255.0 broadcast 192.168.40.255
ether aa:bb:cc:dd:ee:02 txqueuelen 1000 (Ethernet)
After running dpdk-devbind:
Network devices using DPDK-compatible driver
============================================
0000:0d:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' drv=igb_uio
unused=vfio-pci,uio_pci_generic
0000:0d:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' drv=igb_uio
unused=vfio-pci,uio_pci_generic
I have a configuration file:
[use-dpdk=1]
dpdk-mtu=9000
dpdk-corelist=0,1
dpdk-num-mbufs=4096
dpdk-mbuf-cache-size=64
[dpdk-mac=aa:bb:cc:dd:ee:01]
dpdk-lcore = 1
dpdk-ipv4 = 192.168.30.1/24
dpdk-num-desc=4096
[dpdk-mac=aa:bb:cd:dd:ee:02]
dpdk-lcore = 0
dpdk-ipv4 = 192.168.40.1/24
Check for syntax errors in the conf file?
I can't remember whether spaces are allowed around "=" in those config files or
not.
________________________________
The information contained in this message, and any attachments, may contain
privileged and/or proprietary information that is intended solely for the
person or entity to which it is addressed. Moreover, it may contain export
restricted technical data controlled by Export Administration Regulations (EAR)
or the International Traffic in Arms Regulations (ITAR). Any review,
retransmission, dissemination, or re-export to foreign or domestic entities by
anyone other than the intended recipient in accordance with EAR and/or ITAR
regulations is prohibited.
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
