Hi,

we now installed DPDK 17.11 but I still have exactly the same problem.

I have a feeling the problem is that I am not addressing the device correctly. Here is what I did:

The USRP is connected to ethernet interfaces "p1p2" (mac_addr 64:9d:99:b1:1e:8d) and "p1p4" (mac_addr 64:9d:99:b1:1e:8f) which are originally configured with IP addresses 192.168.10.1 and inet_addr 192.168.20.1. This configuration works fine without dpdk.

Then I deactivate these two interfaces using "ifconfig p1p2 down" "ifconfig p1p4 down"and do "dpdk-devbind --bind=vfio-pci 01:00.1" and "dpdk-devbind --bind=vfio-pci 01:00.3". The status of "dpdk-devbind -s" is below.

In the file /etc/uhd/uhd.conf I specify

[dpdk_mac=64:9d:99:b1:1e:8d]
dpdk_io_cpu = 1
dpdk_ipv4 = 192.168.10.1/24

[dpdk_mac=64:9d:99:b1:1e:8f]
dpdk_io_cpu = 2
dpdk_ipv4 = 192.168.20.1/24

Is this the correct way of specifying it? What surprises me is that DPDK requires to address the device by its PCI address while UHD still requires to set the IP addresses.

Florian.

On 1/8/2020 16:19, akin soysal wrote:
Hello all,

Is this problem fixed? If yes, could you please tell how? We have a similar error, so it would be helpful.

Thanks and regards,
Akın

3 Oca 2020 Cum 23:22 tarihinde Sam Reiter via USRP-users <usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>> şunu yazdı:

    Florian,

    DPDK 18.11 is not supported on UHD 3.x. You'll need to use DPDK
    17.11.

    Sam Reiter
    Ettus Research

    On Mon, Dec 23, 2019 at 9:51 AM Florian Kaltenberger via
    USRP-users <usrp-users@lists.ettus.com
    <mailto:usrp-users@lists.ettus.com>> wrote:

        Dear all,

        we have finally managed to set up UHD (3.15) with DPDK (18.11)
        support on our RedHat 7 system (both installed from source)
        with our N310. I have configured the system as explained here
        http://files.ettus.com/manual/page_dpdk.html but when calling

        uhd_usrp_probe --args
        
"use_dpdk=1,mgmt_addr=192.168.12.1,addr=192.168.10.2,second_addr=192.168.20.2,master_clock_rate=122.88e6,type=n3xx"

        I am getting the following runtime error (all the way at the
        bottom):

        [INFO] [UHD] linux; GNU C++ version 4.8.5 20150623 (Red Hat
        4.8.5-39); Boost_106900; UHD_3.15.0.0-0-g4e06022c
        EAL: Detected 10 lcore(s)
        EAL: No free hugepages reported in hugepages-1048576kB
        EAL: Probing VFIO support...
        EAL: VFIO support initialized
        EAL: PCI device 0000:00:19.0 on NUMA socket 0
        EAL:   probe driver: 8086:153a net_e1000_em
        EAL: PCI device 0000:01:00.0 on NUMA socket 0
        EAL:   probe driver: 8086:1572 net_i40e
        EAL: PCI device 0000:01:00.1 on NUMA socket 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:01:00.2 on NUMA socket 0
        EAL:   probe driver: 8086:1572 net_i40e
        EAL: PCI device 0000:01:00.3 on NUMA socket 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!
        [INFO] [MPMD] Initializing 1 device(s) in parallel with args:
        
mgmt_addr=192.168.12.1,type=n3xx,product=n310,serial=31641BC,claimed=False,use_dpdk=1,addr=192.168.10.2,second_addr=192.168.20.2,master_clock_rate=122.88e6
        [INFO] [MPM.PeriphManager] init() called with device args
        
`mgmt_addr=192.168.12.1,product=n310,master_clock_rate=122.88e6,second_addr=192.168.20.2,use_dpdk=1,clock_source=internal,time_source=internal'.
        EAL: Please set IPv4 address for port 0 before opening socket
        [ERROR] [MPMD] Failure during block enumeration:
        AssertionError: _rx_sock != nullptr
          in
        uhd::transport::dpdk_zero_copy_impl::dpdk_zero_copy_impl(const
        uhd::transport::uhd_dpdk_ctx&, unsigned int, const string&,
        const string&, const string&, const
        uhd::transport::zero_copy_xport_params&)

        I am also copying the output of "dpdk-devbind --status" which
        shows that the two interfaces connected to the USRP use the
        vfio-pci driver for DPDK

        Network devices using DPDK-compatible driver
        ============================================
        0000:01:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572'
        drv=vfio-pci unused=i40e
        0000:01:00.3 'Ethernet Controller X710 for 10GbE SFP+ 1572'
        drv=vfio-pci unused=i40e

        Network devices using kernel driver
        ===================================
        0000:00:19.0 'Ethernet Connection I217-LM 153a' if=enp0s25
        drv=e1000e unused=vfio-pci *Active*
        0000:01:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572'
        if=p1p1 drv=i40e unused=vfio-pci
        0000:01:00.2 'Ethernet Controller X710 for 10GbE SFP+ 1572'
        if=p1p3 drv=i40e unused=vfio-pci

        What surprises me is that in the output of the uhd_usrp_probe,
        it does not say it is using the driver for DPDK. any ideas
        what could be wrong?

        Florian.

-- Follow us on Google+
        <https://plus.google.com/+OpenairinterfaceOrg>, LinkedIn
        <https://www.linkedin.com/company/openairinterface>, or
        Twitter <https://twitter.com/osalliance5g>!
        _______________________________________________
        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

    _______________________________________________
    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

--
Follow us on Google+ <https://plus.google.com/+OpenairinterfaceOrg>, LinkedIn <https://www.linkedin.com/company/openairinterface>, or Twitter <https://twitter.com/osalliance5g>!

<<attachment: florian_kaltenberger.vcf>>

_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Reply via email to