Re: [USRP-users] DPDK runtime error

2020-02-06 Thread BERTOLINI Rodolphe via USRP-users 
Hello again,

There seemed to have wrong rights on file, because after changing rights and 
editing the file I had this error:


[INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501; 
UHD_3.15.0.HEAD-0-gaea0e2de
EAL: Detected 28 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device :00:1f.6 on NUMA socket 0
EAL:   probe driver: 8086:15b9 net_e1000_em
EAL: PCI device :17:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
EAL:   using IOMMU type 1 (Type 1)
EAL: Ignore mapping IO port bar(2)
EAL: PCI device :17:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
EAL: Ignore mapping IO port bar(2)
EAL: PCI device :45:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1563 net_ixgbe
EAL: PCI device :45:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1563 net_ixgbe
EAL: Error - exiting with code: 1
  Cause: Requested inactive lcore 3 for port 0


I solved this error by editing again the conf file (it seems that I had to 
remove dpdk-io-core lines)

Now I have again the IPv4 assignement error, with the following configuration :

[use-dpdk=1]
dpdk-mtu=9000
;dpdk-driver=/usr/local/lib/dpdk-pmds/
dpdk-driver=/usr/lib/x86_64-linux-gnu/dpdk-17.11-drivers/
dpdk-corelist=2-4
dpdk-num-mbufs=4096
dpdk-mbuf-cache-size=316
[dpdk-mac=f8:f2:1e:29:c5:14]
dpdk-lcore = 3
;dpdk-io-cpu = 3
dpdk-ipv4 = 192.168.30.2/24
[dpdk-mac=f8:f2:1e:29:c5:15]
dpdk-lcore = 4
;dpdk-io-cpu = 4
dpdk-ipv4 = 192.168.40.2/24
;dpdk-num-desc=4096

It tells me :

EAL: Please set IPv4 address for port 0 before opening socket

I don't get what is wrong. Must both SFP ports of the USRP be plugged, to the 
host?

Regards,
Rodolphe


De : USRP-users [usrp-users-boun...@lists.ettus.com] de la part de BERTOLINI 
Rodolphe via USRP-users [usrp-users@lists.ettus.com]
Envoyé : jeudi 6 février 2020 11:47
À : usrp-users@lists.ettus.com
Objet : Re: [USRP-users] DPDK runtime error

Hello,
Sorry if I had better to create an other thread.

I am trying also to reach better stability in OpenAirInterface, and to use USRP 
through DPDK.
I face the exact same error, however I don't have /etc/uhd folder :

$ locate uhd.conf
/etc/security/limits.d/uhd.conf
/etc/security/limits.d/uhd.conf.dpkg-new

The content of those files is :
@usrp-   rtprio  99

I manually created folder ~/.uhd/, and put a uhd.conf file here (I have read 
somewhere that there are different places where uhd conf file can be located 
depending on system wide or user wide configuration). No success.
Later I also created /etc/uhd folder and copy-pasted the conf file there, still 
no success.

The word separator I used is "-" as you suggested to Florian.

Any thought ?

Also @Florian, do you see any improvement in OAI stability using DPDK with UHD 
3.15?

Thank you.
Regards,
Rodolphe


Hi Aaron,

thanks for spotting this! Indeed that was a mistake. I also had to
adjust the dpdk-num-mbufs=4059 and dpdk-mbuf-cache-size=315 like in the
example configuration file for uhd 3.15.0 and then it worked! Yay!

Now lets see if OpenAirInterface runs more stable with this! :)

Florian.

On 1/8/2020 17:31, Aaron Rossetto via USRP-users wrote:

> Hello Florian,
>
> I believe in UHD 3.15, the keys in the uhd.conf file use dashes (-), not 
> underscores between words, e.g.:
>
> [dpdk-mac=00:11:22:33:44:55]
> dpdk-io-cpu = 1
> dpdk-ipv4 = 192.168.10.1/24
>
> Hope that helps,
> Aaron
>
>
>
> From: USRP-users  lists.ettus.com<http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com>>
>  On Behalf Of Florian Kaltenberger via USRP-users
> Sent: Wednesday, January 8, 2020 10:10 AM
> Subject: [EXTERNAL] Re:DPDK runtime error
>
> 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 PC

Re: [USRP-users] DPDK runtime error

2020-02-06 Thread BERTOLINI Rodolphe via USRP-users 
Hello,
Sorry if I had better to create an other thread.

I am trying also to reach better stability in OpenAirInterface, and to use USRP 
through DPDK.
I face the exact same error, however I don't have /etc/uhd folder :

$ locate uhd.conf
/etc/security/limits.d/uhd.conf
/etc/security/limits.d/uhd.conf.dpkg-new

The content of those files is :
@usrp-   rtprio  99

I manually created folder ~/.uhd/, and put a uhd.conf file here (I have read 
somewhere that there are different places where uhd conf file can be located 
depending on system wide or user wide configuration). No success.
Later I also created /etc/uhd folder and copy-pasted the conf file there, still 
no success.

The word separator I used is "-" as you suggested to Florian.

Any thought ?

Also @Florian, do you see any improvement in OAI stability using DPDK with UHD 
3.15?

Thank you.
Regards,
Rodolphe


Hi Aaron,

thanks for spotting this! Indeed that was a mistake. I also had to
adjust the dpdk-num-mbufs=4059 and dpdk-mbuf-cache-size=315 like in the
example configuration file for uhd 3.15.0 and then it worked! Yay!

Now lets see if OpenAirInterface runs more stable with this! :)

Florian.

On 1/8/2020 17:31, Aaron Rossetto via USRP-users wrote:

> Hello Florian,
>
> I believe in UHD 3.15, the keys in the uhd.conf file use dashes (-), not 
> underscores between words, e.g.:
>
> [dpdk-mac=00:11:22:33:44:55]
> dpdk-io-cpu = 1
> dpdk-ipv4 = 192.168.10.1/24
>
> Hope that helps,
> Aaron
>
>
>
> From: USRP-users  lists.ettus.com>
>  On Behalf Of Florian Kaltenberger via USRP-users
> Sent: Wednesday, January 8, 2020 10:10 AM
> Subject: [EXTERNAL] Re:DPDK runtime error
>
> 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.
>
> ___
> USRP-users mailing list
> USRP-users at 
> lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
--
Follow us on Google+ ,
LinkedIn , or Twitter
!
-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: florian_kaltenberger.vcf
Type: text/x-vcard
Size: 274 bytes
Desc: not available
URL: 

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

Re: [USRP-users] DPDK runtime error

2020-01-09 Thread Florian Kaltenberger via USRP-users 

Hi Aaron,

thanks for spotting this! Indeed that was a mistake. I also had to 
adjust the dpdk-num-mbufs=4059 and dpdk-mbuf-cache-size=315 like in the 
example configuration file for uhd 3.15.0 and then it worked! Yay!


Now lets see if OpenAirInterface runs more stable with this! :)

Florian.

On 1/8/2020 17:31, Aaron Rossetto via USRP-users wrote:


Hello Florian,

I believe in UHD 3.15, the keys in the uhd.conf file use dashes (-), not 
underscores between words, e.g.:

[dpdk-mac=00:11:22:33:44:55]
dpdk-io-cpu = 1
dpdk-ipv4 = 192.168.10.1/24

Hope that helps,
Aaron



From: USRP-users  On Behalf Of Florian 
Kaltenberger via USRP-users
Sent: Wednesday, January 8, 2020 10:10 AM
Subject: [EXTERNAL] Re: [USRP-users] DPDK runtime error

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.

___
USRP-users mailing list
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>!
<>___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] DPDK runtime error

2020-01-08 Thread Aaron Rossetto via USRP-users 
Hello Florian,

I believe in UHD 3.15, the keys in the uhd.conf file use dashes (-), not 
underscores between words, e.g.:

[dpdk-mac=00:11:22:33:44:55]
dpdk-io-cpu = 1
dpdk-ipv4 = 192.168.10.1/24

Hope that helps,
Aaron



From: USRP-users  On Behalf Of Florian 
Kaltenberger via USRP-users
Sent: Wednesday, January 8, 2020 10:10 AM
Subject: [EXTERNAL] Re: [USRP-users] DPDK runtime error

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.

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

Re: [USRP-users] DPDK runtime error

2020-01-08 Thread Florian Kaltenberger via USRP-users 

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 
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 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 :00:19.0 on NUMA socket 0
EAL:   probe driver: 8086:153a net_e1000_em
EAL: PCI device :01:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device :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 :01:00.2 on NUMA socket 0
EAL:   probe driver: 8086:1572 net_i40e
EAL: PCI device :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

Re: [USRP-users] DPDK runtime error

2020-01-08 Thread akin soysal via USRP-users 
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> ş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> 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 :00:19.0 on NUMA socket 0
>> EAL:   probe driver: 8086:153a net_e1000_em
>> EAL: PCI device :01:00.0 on NUMA socket 0
>> EAL:   probe driver: 8086:1572 net_i40e
>> EAL: PCI device :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 :01:00.2 on NUMA socket 0
>> EAL:   probe driver: 8086:1572 net_i40e
>> EAL: PCI device :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
>> 
>> :01:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=vfio-pci
>> unused=i40e
>> :01:00.3 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=vfio-pci
>> unused=i40e
>>
>> Network devices using kernel driver
>> ===
>> :00:19.0 'Ethernet Connection I217-LM 153a' if=enp0s25 drv=e1000e
>> unused=vfio-pci *Active*
>> :01:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' if=p1p1
>> drv=i40e unused=vfio-pci
>> :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+ ,
>> LinkedIn , or Twitter
>> !
>> ___
>> USRP-users mailing list
>> USRP-users@lists.ettus.com
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
> ___
> USRP-users mailing list
>

Re: [USRP-users] DPDK runtime error

2020-01-03 Thread Sam Reiter via USRP-users 
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> 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 :00:19.0 on NUMA socket 0
> EAL:   probe driver: 8086:153a net_e1000_em
> EAL: PCI device :01:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device :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 :01:00.2 on NUMA socket 0
> EAL:   probe driver: 8086:1572 net_i40e
> EAL: PCI device :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
> 
> :01:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=vfio-pci
> unused=i40e
> :01:00.3 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=vfio-pci
> unused=i40e
>
> Network devices using kernel driver
> ===
> :00:19.0 'Ethernet Connection I217-LM 153a' if=enp0s25 drv=e1000e
> unused=vfio-pci *Active*
> :01:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' if=p1p1
> drv=i40e unused=vfio-pci
> :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+ ,
> LinkedIn , or Twitter
> !
> ___
> USRP-users mailing list
> 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
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com