Changed the driver string but the problem persists. Is it problematic that the
NIC is on the last PCIe slot of the motherboard (same NUMA socket)?
I attached the command I'm giving and the output.
Thanks,
Lorenzo
________________________________
From: Sam Reiter <sam.rei...@ettus.com>
Sent: Monday, January 6, 2020 2:05 PM
To: Minutolo, Lorenzo <minut...@caltech.edu>
Cc: usrp-users@lists.ettus.com <usrp-users@lists.ettus.com>
Subject: Re: [USRP-users] dpdk with x300
That should be fine.
Looking over those screenshots again, you'll need to change your dpdk driver
path in uhd.conf. Here's what the uncommented parts of uhd.conf should look
like for 17.11:
[use_dpdk=1]
dpdk-mtu=9000
dpdk-driver=/usr/lib/x86_64-linux-gnu/dpdk-17.11-drivers/
dpdk-corelist=1,2,3
dpdk-num-mbufs=4095
dpdk-mbufs-cache-size=315
[dpdk-mac=aa:bb:cc:dd:ee:f1]
dpdk-io-cpu = 2
dpdk-ipv4 = 192.168.10.1/24<http://192.168.10.1/24>
[dpdk-mac=aa:bb:cc:dd:ee:f2]
dpdk-io-cpu = 3
dpdk-ipv4 = 192.168.20.1/24<http://192.168.20.1/24>
Note that the IP and MAC need to be changed for your machine.
Sam Reiter
Ettus Research
On Mon, Jan 6, 2020 at 3:29 PM Minutolo, Lorenzo
<minut...@caltech.edu<mailto:minut...@caltech.edu>> wrote:
I' using:
dpdk-procinfo -v
EAL: Detected 16 lcore(s)
EAL: RTE Version: 'DPDK 17.11.9'
Thanks,
Lorenzo
________________________________
From: Sam Reiter <sam.rei...@ettus.com<mailto:sam.rei...@ettus.com>>
Sent: Monday, January 6, 2020 8:27 AM
To: Minutolo, Lorenzo <minut...@caltech.edu<mailto:minut...@caltech.edu>>
Cc: usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>
<usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>>
Subject: Re: [USRP-users] dpdk with x300
Lorenzo,
What version of DPDK are you using?
Sam Reiter
Ettus Research
On Fri, Jan 3, 2020 at 8:20 PM Minutolo, Lorenzo via USRP-users
<usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>> wrote:
Hi All,
I'm using an x300 connected via a Intel X710 to a machine running Ubuntu 18.04.
I'm using the recently released UHD 3.15 LTS.
I'm trying to follow the guide to connect via dpdk. Everything in the guide on
the Ettus website works however when launching uhd_usrp_probe (as sudo
uhd_usrp_probe --args "address = 192.168.30.2, use_dpdk=1") I get the output
reported in the output.png attachment. My actual dpdk-devbind.py --status is
reported in status.png attachment as well as the uhd.conf I'm using.
What am I doing wrong?
In the configuration file I tried altering the cores to see if that was an
issue but nothing changed.
Thanks,
Lorenzo
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com<mailto:USRP-users@lists.ettus.com>
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
lebicep@GPUserver:~$ sudo uhd_usrp_probe --args "addr = 192.168.40.2,
second_addr = 192.168.30.2, use_dpdk =1"
[INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106600;
UHD_3.15.0.0-124-geb448043
EAL: Detected 16 lcore(s)
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:00:1f.6 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:15bc net_e1000_em
EAL: PCI device 0000:02:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:02:00.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1572 net_i40e
EAL: using IOMMU type 1 (Type 1)
PMD: Global register is changed during enable FDIR flexible payload
PMD: Global register is changed during support QinQ parser
PMD: Global register is changed during configure hash input set
PMD: Global register is changed during configure fdir mask
PMD: Global register is changed during configure hash mask
PMD: Global register is changed during support QinQ cloud filter
PMD: Global register is changed during support TPID configuration
EAL: PCI device 0000:03:00.1 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:03:00.2 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1572 net_i40e
EAL: PCI device 0000:03:00.3 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 8086:1572 net_i40e
PMD: Global register is changed during enable FDIR flexible payload
PMD: Global register is changed during support QinQ parser
PMD: Global register is changed during configure hash input set
PMD: Global register is changed during configure fdir mask
PMD: Global register is changed during configure hash mask
PMD: Global register is changed during support QinQ cloud filter
PMD: Global register is changed during support TPID configuration
EAL: Waiting for links to come up...
EAL: Init DONE!
EAL: Starting I/O threads!
EAL: Please set IPv4 address for port 0 before opening socket
[ERROR] [X300] X300 Network discovery error AssertionError: _rx_sock != nullptr
in
uhd::transport::dpdk_simple_impl::dpdk_simple_impl(uhd::transport::uhd_dpdk_ctx&,
const string&, const string&, bool)
at /home/lebicep/Documents/uhd/host/lib/transport/dpdk_simple.cpp:44
Error: LookupError: KeyError: No devices found for ----->
Device Address:
addr: 192.168.40.2
second_addr: 192.168.30.2
use_dpdk: 1
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
