[USRP-users] dpdk with x300
sam.reiter at ettus.com
Mon Jan 6 17:05:05 EST 2020
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:
dpdk-io-cpu = 2
dpdk-ipv4 = 192.168.10.1/24
dpdk-io-cpu = 3
dpdk-ipv4 = 192.168.20.1/24
Note that the IP and MAC need to be changed for your machine.
On Mon, Jan 6, 2020 at 3:29 PM Minutolo, Lorenzo <minutolo at caltech.edu>
> I' using:
> dpdk-procinfo -v
> EAL: Detected 16 lcore(s)
> EAL: RTE Version: '*DPDK 17.11.9'*
> *From:* Sam Reiter <sam.reiter at ettus.com>
> *Sent:* Monday, January 6, 2020 8:27 AM
> *To:* Minutolo, Lorenzo <minutolo at caltech.edu>
> *Cc:* usrp-users at lists.ettus.com <usrp-users at lists.ettus.com>
> *Subject:* Re: [USRP-users] dpdk with x300
> 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 at 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
> What am I doing wrong?
> In the configuration file I tried altering the cores to see if that was an
> issue but nothing changed.
> USRP-users mailing list
> USRP-users at lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the USRP-users