I have used DPDK with the X310. I don't recall specifically, but I'm
pretty sure you either...
a) don't specify mgmt_addr, or
b) specify it the same as addr
On Tue, Jul 21, 2020 at 12:12 PM Marcus D. Leech via USRP-users <
usrp-users@lists.ettus.com> wrote:
> On 07/21/2020 10:53 AM, Carmichael,
On 07/21/2020 10:53 AM, Carmichael, Ryan via USRP-users wrote:
On the DPDK page (https://files.ettus.com/manual/page_dpdk.html) the
following statement is made:
“Device discovery via DPDK is not currently implemented, so the device
args |mgmt_addr|, |addr|, and |second_addr| (if applicable)
On 07/21/2020 10:53 AM, Carmichael, Ryan via USRP-users wrote:
On the DPDK page (https://files.ettus.com/manual/page_dpdk.html) the
following statement is made:
“Device discovery via DPDK is not currently implemented, so the device
args |mgmt_addr|, |addr|, and |second_addr| (if applicable)
On the DPDK page (https://files.ettus.com/manual/page_dpdk.html) the following
statement is made:
"Device discovery via DPDK is not currently implemented, so the device args
mgmt_addr, addr, and second_addr (if applicable) must all be specified at
runtime. There is no mechanism for MPM's TCP/IP
