[ovs-discuss] can ovn loadblance replace the openstack lbaas?
hi all: I have a question about the use of ovn-loadblace, how about using ovn-loadblance to work with haproxy in openstack-lbaas, and ovn-loadblance acts as level4(ip+port), while haproxy acts as level7 ? Will this method work well? Thanks.___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] ovs-2.8 Cannot open /dev/uio0
I rpmed the ovs-dpdk local, and installed the ovs.rpm in my VM.
local bulid the dpdk.rpm and ovs.rpm:
638 rpm -ivh dpdk-16.11.3-1.x86_64.rpm
639 rpm -ivh dpdk-devel-16.11.3-1.x86_64.rpm
./boot.sh && ./configure
make rpm-fedora RPMBUILD_OPT="--with dpdk --without check"
In the VM:
689 rpm -ivh dpdk-17.05.2-1.x86_64.rpm
690 rpm -ivh dpdk-devel-17.05.2-1.x86_64.rpm
692 rpm -ivh openvswitch-2.8.1-1.el7.centos.x86_64.rpm
Then, the configure Hugepages/igb_uio, and bind the NIC with igb_uio.
在 2017-11-23 22:26:00，"O'Reilly, Darragh" <darragh.orei...@hpe.com> 写道：
How was ovs installed? I don’t recall ever seeing ovs-vswitchd running as a
non-root user.
From:王嵘 [mailto:rong.w...@easystack.cn]
Sent: 23 November 2017 13:09
To: O'Reilly, Darragh <darragh.orei...@hpe.com>
Cc:ovs-discuss@openvswitch.org
Subject: Re:RE: [ovs-discuss] ovs-2.8 Cannot open /dev/uio0
O, my fault.
And now find the log like :
2017-11-23T13:02:43.869Z|00071|dpdk|ERR|EAL: Cannot open /dev/uio0: Permission
denied
2017-11-23T13:02:43.869Z|00072|dpdk|ERR|EAL: Current userid: 988
The uid 988 belongs to the lbvirt? why the uid is 988?
And even this uid don't have the right to open the uio0。
[root@localhost rpm-2.8]# cat /etc/group | grep openvswitch
openvswitch:x:983:
hugetlbfs:x:1001:openvswitch
[root@localhost rpm-2.8]# cat /etc/group | grep 988
libvirt:x:988:
[root@localhost rpm-2.8]#
在 2017-11-23 20:24:04，"O'Reilly, Darragh" <darragh.orei...@hpe.com> 写道：
I think you got the address of the function getuid, but you want to call it by
adding ():
RTE_LOG(ERR, EAL, "Current userid: %d\n", getuid() );
From:ovs-discuss-boun...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of ??
Sent: 23 November 2017 08:20
To:王嵘 <rong.w...@easystack.cn>
Cc:ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] ovs-2.8 Cannot open /dev/uio0
And I add a log in the code, found thath the current uid is not 0(root),
if there is some other config I missed ?
/* save fd if in primary process */
dev->intr_handle.fd = open(devname, O_RDWR);
if (dev->intr_handle.fd < 0) {
RTE_LOG(ERR, EAL, "Cannot open %s: %s\n",
devname, strerror(errno));
RTE_LOG(ERR, EAL, "Current userid: %d\n", getuid);
goto error;
}
#systemctl restart openvswitch
2017-11-23T07:57:13.476Z|00071|dpdk|ERR|EAL: Cannot open /dev/uio0: Permission
denied
2017-11-23T07:57:13.476Z|00072|dpdk|ERR|EAL: Current userid: -534781824
在 2017-11-22 21:05:05，"王嵘" <rong.w...@easystack.cn> 写道：
hi,
That's because I'm using the Broadcom Nic for performing-test and found the
uio problem("Cannot open /dev/uio0: Permission denied").
and I now RECHECKED the problem in my own VM environment。
Pity that, the uio Permission denied problem still alway exists.(the ovs2.7 is
ok).
and the ovs is 2.8.1, dpdk-1705.2
[root@localhost test]# rpm -qa | grep openvswitch
openvswitch-2.8.1-1.el7.centos.x86_64
openvswitch-debuginfo-2.8.1-1.el7.centos.x86_64
[root@localhost test]# rpm -qa | grep dpdk
dpdk-17.05.2-1.x86_64
dpdk-devel-17.05.2-1.x86_64
dpdk-debuginfo-17.05.2-1.x86_64
2017-11-22T11:37:24.909Z|00061|dpdk|WARN|EAL: rte_pci_probe_one execing.
2017-11-22T11:37:24.909Z|00062|dpdk|INFO|EAL: PCI device :00:09.0 on NUMA
socket -1
2017-11-22T11:37:24.909Z|00063|dpdk|INFO|EAL: probe driver: 8086:100e
net_e1000_em
2017-11-22T11:37:24.909Z|00064|dpdk|ERR|EAL: Cannot open /dev/uio0: Permission
denied
2017-11-22T11:37:24.909Z|00065|dpdk|WARN|EAL: Requested device :00:09.0
cannot be used
2017-11-22T11:37:24.909Z|00066|dpdk|ERR|EAL: Driver cannot attach the device
(:00:09.0)
[root@localhost test]# dpdk-devbind --status
Network devices using DPDK-compatible driver
:00:09.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio unused=
:00:0a.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio unused=
Network devices using kernel driver
===
:00:03.0 'Virtio network device 1000' if=eth0 drv=virtio-pci unused=igb_uio
*Active*
[root@localhost test]# lspci | egrep -i --color 'network|ethernet'
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
00:09.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 03)
00:0a.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 03)
[root@localhost test]# lshw -c network -businfo
Bus info Device Class Description
pci@:00:03.0 networkVirtio network device
virtio@0 eth0networkEthernet interface
pci@:00:09.0 network82540EM Gigabit Ethernet Controller
pci@:00:0a.0
Re: [ovs-discuss] ovs-2.8 Cannot open /dev/uio0
O, my fault.
And now find the log like :
2017-11-23T13:02:43.869Z|00071|dpdk|ERR|EAL: Cannot open /dev/uio0: Permission
denied
2017-11-23T13:02:43.869Z|00072|dpdk|ERR|EAL: Current userid: 988
The uid 988 belongs to the lbvirt? why the uid is 988?
And even this uid don't have the right to open the uio0。
[root@localhost rpm-2.8]# cat /etc/group | grep openvswitch
openvswitch:x:983:
hugetlbfs:x:1001:openvswitch
[root@localhost rpm-2.8]# cat /etc/group | grep 988
libvirt:x:988:
[root@localhost rpm-2.8]#
在 2017-11-23 20:24:04，"O'Reilly, Darragh" <darragh.orei...@hpe.com> 写道：
I think you got the address of the function getuid, but you want to call it by
adding ():
RTE_LOG(ERR, EAL, "Current userid: %d\n", getuid() );
From:ovs-discuss-boun...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of ??
Sent: 23 November 2017 08:20
To:王嵘 <rong.w...@easystack.cn>
Cc:ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] ovs-2.8 Cannot open /dev/uio0
And I add a log in the code, found thath the current uid is not 0(root),
if there is some other config I missed ?
/* save fd if in primary process */
dev->intr_handle.fd = open(devname, O_RDWR);
if (dev->intr_handle.fd < 0) {
RTE_LOG(ERR, EAL, "Cannot open %s: %s\n",
devname, strerror(errno));
RTE_LOG(ERR, EAL, "Current userid: %d\n", getuid);
goto error;
}
#systemctl restart openvswitch
2017-11-23T07:57:13.476Z|00071|dpdk|ERR|EAL: Cannot open /dev/uio0: Permission
denied
2017-11-23T07:57:13.476Z|00072|dpdk|ERR|EAL: Current userid: -534781824
在 2017-11-22 21:05:05，"王嵘" <rong.w...@easystack.cn> 写道：
hi,
That's because I'm using the Broadcom Nic for performing-test and found the
uio problem("Cannot open /dev/uio0: Permission denied").
and I now RECHECKED the problem in my own VM environment。
Pity that, the uio Permission denied problem still alway exists.(the ovs2.7 is
ok).
and the ovs is 2.8.1, dpdk-1705.2
[root@localhost test]# rpm -qa | grep openvswitch
openvswitch-2.8.1-1.el7.centos.x86_64
openvswitch-debuginfo-2.8.1-1.el7.centos.x86_64
[root@localhost test]# rpm -qa | grep dpdk
dpdk-17.05.2-1.x86_64
dpdk-devel-17.05.2-1.x86_64
dpdk-debuginfo-17.05.2-1.x86_64
2017-11-22T11:37:24.909Z|00061|dpdk|WARN|EAL: rte_pci_probe_one execing.
2017-11-22T11:37:24.909Z|00062|dpdk|INFO|EAL: PCI device :00:09.0 on NUMA
socket -1
2017-11-22T11:37:24.909Z|00063|dpdk|INFO|EAL: probe driver: 8086:100e
net_e1000_em
2017-11-22T11:37:24.909Z|00064|dpdk|ERR|EAL: Cannot open /dev/uio0: Permission
denied
2017-11-22T11:37:24.909Z|00065|dpdk|WARN|EAL: Requested device :00:09.0
cannot be used
2017-11-22T11:37:24.909Z|00066|dpdk|ERR|EAL: Driver cannot attach the device
(:00:09.0)
[root@localhost test]# dpdk-devbind --status
Network devices using DPDK-compatible driver
:00:09.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio unused=
:00:0a.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio unused=
Network devices using kernel driver
===
:00:03.0 'Virtio network device 1000' if=eth0 drv=virtio-pci unused=igb_uio
*Active*
[root@localhost test]# lspci | egrep -i --color 'network|ethernet'
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
00:09.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 03)
00:0a.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 03)
[root@localhost test]# lshw -c network -businfo
Bus info Device Class Description
pci@:00:03.0 networkVirtio network device
virtio@0 eth0networkEthernet interface
pci@:00:09.0 network82540EM Gigabit Ethernet Controller
pci@:00:0a.0 network82540EM Gigabit Ethernet Controller
br0 networkEthernet interface
ovs-system networkEthernet interface
virbr0-nic networkEthernet interface
virbr0 networkEthernet interface
在 2017-11-16 02:21:54，"Shivaram Mysore" <shivaram.mys...@gmail.com> 写道：
Glad to hear that you solved the problem.
What you have are Intel NIC - 82540em. The driver igb_uio should work for this
- which is what you have. I am confused as to why you said that you were using
Broadcom Nextreme card
Anyways, it is good to hear that you were able to rectify the issue.
On Wed, Nov 15, 2017 at 4:40 AM, 王嵘 <rong.w...@easystack.cn> wrote:
hi, I solved the NIC bind problem.
I checked the log found that
netdev_dpdk|ERR|Interface dpdk-eth2(rxq:1 txq:3) configure error: Invalid
ar
Re: [ovs-discuss] ovs-2.8 Cannot open /dev/uio0
hi,
That's because I'm using the Broadcom Nic for performing-test and found the
uio problem("Cannot open /dev/uio0: Permission denied").
and I now RECHECKED the problem in my own VM environment。
Pity that, the uio Permission denied problem still alway exists.(the ovs2.7 is
ok).
and the ovs is 2.8.1, dpdk-1705.2
[root@localhost test]# rpm -qa | grep openvswitch
openvswitch-2.8.1-1.el7.centos.x86_64
openvswitch-debuginfo-2.8.1-1.el7.centos.x86_64
[root@localhost test]# rpm -qa | grep dpdk
dpdk-17.05.2-1.x86_64
dpdk-devel-17.05.2-1.x86_64
dpdk-debuginfo-17.05.2-1.x86_64
2017-11-22T11:37:24.909Z|00061|dpdk|WARN|EAL: rte_pci_probe_one execing.
2017-11-22T11:37:24.909Z|00062|dpdk|INFO|EAL: PCI device :00:09.0 on NUMA
socket -1
2017-11-22T11:37:24.909Z|00063|dpdk|INFO|EAL: probe driver: 8086:100e
net_e1000_em
2017-11-22T11:37:24.909Z|00064|dpdk|ERR|EAL: Cannot open /dev/uio0: Permission
denied
2017-11-22T11:37:24.909Z|00065|dpdk|WARN|EAL: Requested device :00:09.0
cannot be used
2017-11-22T11:37:24.909Z|00066|dpdk|ERR|EAL: Driver cannot attach the device
(:00:09.0)
[root@localhost test]# dpdk-devbind --status
Network devices using DPDK-compatible driver
:00:09.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio unused=
:00:0a.0 '82540EM Gigabit Ethernet Controller 100e' drv=igb_uio unused=
Network devices using kernel driver
===
:00:03.0 'Virtio network device 1000' if=eth0 drv=virtio-pci unused=igb_uio
*Active*
[root@localhost test]# lspci | egrep -i --color 'network|ethernet'
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
00:09.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 03)
00:0a.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 03)
[root@localhost test]# lshw -c network -businfo
Bus info Device Class Description
pci@:00:03.0 networkVirtio network device
virtio@0 eth0networkEthernet interface
pci@:00:09.0 network82540EM Gigabit Ethernet Controller
pci@:00:0a.0 network82540EM Gigabit Ethernet Controller
br0 networkEthernet interface
ovs-system networkEthernet interface
virbr0-nic networkEthernet interface
virbr0 networkEthernet interface
在 2017-11-16 02:21:54，"Shivaram Mysore" <shivaram.mys...@gmail.com> 写道：
Glad to hear that you solved the problem.
What you have are Intel NIC - 82540em. The driver igb_uio should work for this
- which is what you have. I am confused as to why you said that you were using
Broadcom Nextreme card
Anyways, it is good to hear that you were able to rectify the issue.
On Wed, Nov 15, 2017 at 4:40 AM, 王嵘 <rong.w...@easystack.cn> wrote:
hi, I solved the NIC bind problem.
I checked the log found that
netdev_dpdk|ERR|Interface dpdk-eth2(rxq:1 txq:3) configure error: Invalid
argument
so, I changed the rxq of the NIC to 3 by "options:n_rxq=3", and it works. ^^
I tested the ovs2.8-dpdk in another VM of Centos7, but the "Permission denied"
problem still exists.
Here is the results of the commands you asked to execute,
[root@localhost ~]# lshw -c network -businfo
Bus info Device Class Description
pci@:00:03.0 networkVirtio network device
virtio@0 eth0networkEthernet interface
pci@:00:09.0 network82540EM Gigabit Ethernet Controller
pci@:00:0a.0 ens10 network82540EM Gigabit Ethernet Controller
br0 networkEthernet interface
ovs-netdev networkEthernet interface
virbr0-nic networkEthernet interface
virbr0 networkEthernet interface
[root@localhost ~]# lspci | egrep -i --color 'network|ethernet'
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
00:09.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 03)
00:0a.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 03)
[root@localhost ~]# lsmod | grep uio
igb_uio13224 1
uio19259 3 igb_uio
[root@localhost test]# lsmod | grep uio
igb_uio13224 0
uio19259 1 igb_uio
在 2017-11-15 04:29:34，"Shivaram Mysore" <shivaram.mys...@gmail.com> 写道：
What is the output of the following commands:
lshw -c network -businfo
lspci | egrep -i --color 'network|ethernet'
lsmod | grep uio
/sbin/dp
[ovs-discuss] Will fragment be processed in userspace(dpdk) connection track
hi, I am using ovs-dpdk now, and find that the fragment has not been processed before the userspace connection track, which is very necessary for me to use. And I want to know, whether this function will be added? Thanks very much. WangRong Best Regards. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] ovs-2.8 Cannot open /dev/uio0
hi, I solved the NIC bind problem. I checked the log found that netdev_dpdk|ERR|Interface dpdk-eth2(rxq:1 txq:3) configure error: Invalid argument so, I changed the rxq of the NIC to 3 by "options:n_rxq=3", and it works. ^^ I tested the ovs2.8-dpdk in another VM of Centos7, but the "Permission denied" problem still exists. Here is the results of the commands you asked to execute, [root@localhost ~]# lshw -c network -businfo Bus info Device Class Description pci@:00:03.0 networkVirtio network device virtio@0 eth0networkEthernet interface pci@:00:09.0 network82540EM Gigabit Ethernet Controller pci@:00:0a.0 ens10 network82540EM Gigabit Ethernet Controller br0 networkEthernet interface ovs-netdev networkEthernet interface virbr0-nic networkEthernet interface virbr0 networkEthernet interface [root@localhost ~]# lspci | egrep -i --color 'network|ethernet' 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:09.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03) 00:0a.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03) [root@localhost ~]# lsmod | grep uio igb_uio13224 1 uio19259 3 igb_uio 在 2017-11-15 04:29:34，"Shivaram Mysore" <shivaram.mys...@gmail.com> 写道： What is the output of the following commands: lshw -c network -businfo lspci | egrep -i --color 'network|ethernet' lsmod | grep uio /sbin/dpdk-devbind --status On Mon, Nov 13, 2017 at 9:29 PM, 王嵘 <rong.w...@easystack.cn> wrote: I just want to use ovs-2.8 for userspace connection-track, and I choose the latest LST DPDK 1705. But, you mean theres is something like broadcom-uio.ko when using broadcom NIC? I just have changed the config/common_base: CONFIG_RTE_LIBRTE_BNX2X_PMD=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=y CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC=y 在 2017-11-14 12:49:44，"Shivaram Mysore" <shivaram.mys...@gmail.com> 写道： Is there a specific reason as to why you would want to use this version of DPDK? I have never had to check permission. Also, igb is mainly for Intel NICs. You are using a Broadcom NIC - http://dpdk.org/doc/guides/nics/bnxt.html for driver info. I think what you have is a misconfiguration. You may want to check out the scripts here https://github.com/shivarammysore/faucetsdn-intel/tree/master/src/ubuntu/zesty/ovs_281 - to setup and configure DPDK. I have only used Intel NICs. Cheers! On Mon, Nov 13, 2017 at 6:50 PM, 王嵘 <rong.w...@easystack.cn> wrote: hi, I'm using ovs2.8 with dpdk-17052, and the 'NetXtreme II BCM57810 10 Gigabit Ethernet 168e'. There comes the error, while I try to bind the NIC using igb_uio. 2017-11-14T02:25:18.400Z|00362|dpdk|INFO|EAL: probe driver: 14e4:168e net_bnx2x 2017-11-14T02:25:18.400Z|00363|dpdk|ERR|EAL: Cannot open /dev/uio0: Permission denied Then I chmod the file, like "chmod 777 /dev/uio0",(but I dont think this is right way.) but there comes other files with the same error, and I also chmod them. And I do the actions: chmod 777 /sys/bus/pci/devices/:20:00.1/* chmod 777 /sys/class/uio/uio0/device/config Then , restart the ovs-dpdk, But, there comes the following error: 2017-11-14T02:40:05.436Z|8384580|dpdk|ERR|PMD: pci_read(): Can't read from PCI config space 2017-11-14T02:40:05.436Z|8384581|dpdk|ERR|PMD: pci_read(): Can't read from PCI config space 2017-11-14T02:40:05.436Z|8384582|dpdk|ERR|PMD: pci_read(): Can't read from PCI config space 2017-11-14T02:40:05.436Z|8384583|dpdk|ERR|PMD: pci_read(): Can't read from PCI config space 2017-11-14T02:40:05.436Z|8384584|dpdk|INFO|PMD: bnx2x_pci_get_caps(): Failed to allocate memory 2017-11-14T02:40:05.436Z|8384585|dpdk|INFO|PMD: bnx2x_attach(): PCIe caps reading was failed 2017-11-14T02:40:05.436Z|8384586|dpdk|ERR|PMD: bnx2x_common_dev_init(): bnx2x_attach failed (-12) 2017-11-14T02:40:05.436Z|8384587|dpdk|ERR|EAL: Requested device :20:00.1 cannot be used So, why there comes the Permission prolem? And what should I do for the PCIe error? Or it is the NIC drivers' problem? Thanks a lot. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] ovs-2.8 Cannot open /dev/uio0
I just want to use ovs-2.8 for userspace connection-track, and I choose the latest LST DPDK 1705. But, you mean theres is something like broadcom-uio.ko when using broadcom NIC? I just have changed the config/common_base: CONFIG_RTE_LIBRTE_BNX2X_PMD=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=y CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC=y 在 2017-11-14 12:49:44，"Shivaram Mysore" <shivaram.mys...@gmail.com> 写道： Is there a specific reason as to why you would want to use this version of DPDK? I have never had to check permission. Also, igb is mainly for Intel NICs. You are using a Broadcom NIC - http://dpdk.org/doc/guides/nics/bnxt.html for driver info. I think what you have is a misconfiguration. You may want to check out the scripts here https://github.com/shivarammysore/faucetsdn-intel/tree/master/src/ubuntu/zesty/ovs_281 - to setup and configure DPDK. I have only used Intel NICs. Cheers! On Mon, Nov 13, 2017 at 6:50 PM, 王嵘 <rong.w...@easystack.cn> wrote: hi, I'm using ovs2.8 with dpdk-17052, and the 'NetXtreme II BCM57810 10 Gigabit Ethernet 168e'. There comes the error, while I try to bind the NIC using igb_uio. 2017-11-14T02:25:18.400Z|00362|dpdk|INFO|EAL: probe driver: 14e4:168e net_bnx2x 2017-11-14T02:25:18.400Z|00363|dpdk|ERR|EAL: Cannot open /dev/uio0: Permission denied Then I chmod the file, like "chmod 777 /dev/uio0",(but I dont think this is right way.) but there comes other files with the same error, and I also chmod them. And I do the actions: chmod 777 /sys/bus/pci/devices/:20:00.1/* chmod 777 /sys/class/uio/uio0/device/config Then , restart the ovs-dpdk, But, there comes the following error: 2017-11-14T02:40:05.436Z|8384580|dpdk|ERR|PMD: pci_read(): Can't read from PCI config space 2017-11-14T02:40:05.436Z|8384581|dpdk|ERR|PMD: pci_read(): Can't read from PCI config space 2017-11-14T02:40:05.436Z|8384582|dpdk|ERR|PMD: pci_read(): Can't read from PCI config space 2017-11-14T02:40:05.436Z|8384583|dpdk|ERR|PMD: pci_read(): Can't read from PCI config space 2017-11-14T02:40:05.436Z|8384584|dpdk|INFO|PMD: bnx2x_pci_get_caps(): Failed to allocate memory 2017-11-14T02:40:05.436Z|8384585|dpdk|INFO|PMD: bnx2x_attach(): PCIe caps reading was failed 2017-11-14T02:40:05.436Z|8384586|dpdk|ERR|PMD: bnx2x_common_dev_init(): bnx2x_attach failed (-12) 2017-11-14T02:40:05.436Z|8384587|dpdk|ERR|EAL: Requested device :20:00.1 cannot be used So, why there comes the Permission prolem? And what should I do for the PCIe error? Or it is the NIC drivers' problem? Thanks a lot. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] hardware offloading in ovs-2.8
hi, I used the GDB the l2fwd for debug, and found the errors like this: DPDK log error is : MD: bnx2x_link_report(): NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit PMD: bnx2x_interrupt_action(): Interrupt handled PMD: bnx2x_attn_int_deasserted2(): PXP2_REG_PXP2_INT_STS_CLR_0 0x0080 PMD: bnx2x_attn_int_deasserted2(): PXP2_WR_PGLUE_EOP_ERROR PMD: bnx2x_attn_int_deasserted2(): FATAL HW block attention set2 0x20 PANIC in bnx2x_attn_int_deasserted2(): and the bt : (gdb) bt #0 0x76f111d7 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x76f128c8 in __GI_abort () at abort.c:90 #2 0x004a4c58 in __rte_panic (funcname=0x93ef30 <__func__.18256> "bnx2x_attn_int_deasserted2", format=0x93c1f7 "HW block attention set2%.0s") at /home/dpdk-17.05.2/lib/librte_eal/linuxapp/eal/eal_debug.c:90 #3 0x005082bd in bnx2x_attn_int_deasserted2 (sc=0x7ffd73dc89c0, attn=32) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:3978 #4 0x00508753 in bnx2x_attn_int_deasserted (sc=0x7ffd73dc89c0, deasserted=1) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:4097 #5 0x005089cc in bnx2x_attn_int (sc=0x7ffd73dc89c0) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:4167 #6 0x00509360 in bnx2x_handle_sp_tq (sc=0x7ffd73dc89c0) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:4462 #7 0x005095f4 in bnx2x_intr_legacy (sc=0x7ffd73dc89c0, scan_fp=0) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:4556 #8 0x0053579d in bnx2x_interrupt_action (dev=0xc7e100 ) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x_ethdev.c:111 #9 0x00535854 in bnx2x_interrupt_handler (param=0xc7e100 ) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x_ethdev.c:128 #10 0x004a6469 in eal_intr_process_interrupts (events=0x766d9cf0, nfds=1) at /home/dpdk-17.05.2/lib/librte_eal/linuxapp/eal/eal_interrupts.c:747 #11 0x004a65de in eal_intr_handle_interrupts (pfd=16, totalfds=2) at /home/dpdk-17.05.2/lib/librte_eal/linuxapp/eal/eal_interrupts.c:794 #12 0x004a675a in eal_intr_thread_main (arg=0x0) at /home/dpdk-17.05.2/lib/librte_eal/linuxapp/eal/eal_interrupts.c:864 #13 0x772a4dc5 in start_thread (arg=0x766da700) at pthread_create.c:308 #14 0x76fd373d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Does this mean ,the is the NIC driver's problem? 在 2017-11-09 20:46:37，"Flavio Leitner" <f...@sysclose.org> 写道： >On Thu, 9 Nov 2017 18:07:05 +0800 (CST) >王嵘 <rong.w...@easystack.cn> wrote: > >> hi, >> I rpmbuild the ovs-dpdk by myself, and the "config/common_base" : >> CONFIG_RTE_LIBRTE_BNX2X_PMD=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=y >> CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC=y >> >> then ,I build the rpm of dpdk/dpdk-devel，and installed the 2 rpms to >> rpmbuild the ovs-dpdk。 >> when I used the ovs-dpdk with the bcm-NIC, there comes the error： >> >> here is the error in "/var/log/openvswitch/ovs-vswitchd.log" >> 2017-11-09T09:28:30.038Z|16773336|dpdk|INFO|EAL: PCI device :20:00.1 on >> NUMA socket 0 >> 2017-11-09T09:28:30.038Z|16773337|dpdk|INFO|EAL: probe driver: 14e4:168e >> net_bnx2x >> 2017-11-09T09:28:30.038Z|16773338|dpdk|WARN|EAL: Requested device >> :20:00.1 cannot be used >> 2017-11-09T09:28:30.038Z|16773339|dpdk|ERR|EAL: Driver cannot attach the >> device (:20:00.1) >> 2017-11-09T09:28:30.038Z|16773340|netdev_dpdk|WARN|Error attaching device >> ':20:00.1' to DPDK >> 2017-11-09T09:28:30.038Z|16773341|netdev|WARN|dpdk-eth2: could not set >> configuration (Invalid argument) > > >Looks like DPDK has the pmd enabled and has identified the device. >Did you bind the NIC to the VFIO driver before start OVS? > > >> And, my NIC firmware is : >> [root@node-4 ~]# ethtool -i eth2 >> driver: bnx2x >> version: 1.712.30-0 >> firmware-version: bc 7.0.49 >> expansion-rom-version: >> bus-info: :20:00.1 >> supports-statistics: yes >> supports-test: yes >> supports-eeprom-access: yes >> supports-register-dump: yes >> supports-priv-flags: yes >> >> >> Does the fm version not satisfies ? or some other reasons ? > >I don't know about FW versions. >fbl > > >> >> >> >> >> >> >> 在 2017-11-08 21:28:01，"Flavio Leitner" <f...@sysclose.org> 写道： >> >On Wed, 8 Nov 2017 11:15:00 +0800 (CST) >> >王嵘 <rong.w...@easystack.cn> wrote: >> > &g
Re: [ovs-discuss] hardware offloading in ovs-2.8
I used the igb_uio, not the vfio-pci. and, when i bind the vfio , error like this: [root@node-4 ~]# modprobe vfio-pci [root@node-4 ~]# dpdk-devbind --bind=vfio-pci eth2 Error: bind failed for :20:00.1 - Cannot bind to driver vfio-pci Error: unbind failed for :20:00.1 - Cannot open /sys/bus/pci/drivers//unbind 在 2017-11-09 20:46:37，"Flavio Leitner" <f...@sysclose.org> 写道： >On Thu, 9 Nov 2017 18:07:05 +0800 (CST) >王嵘 <rong.w...@easystack.cn> wrote: > >> hi, >> I rpmbuild the ovs-dpdk by myself, and the "config/common_base" : >> CONFIG_RTE_LIBRTE_BNX2X_PMD=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=y >> CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC=y >> >> then ,I build the rpm of dpdk/dpdk-devel，and installed the 2 rpms to >> rpmbuild the ovs-dpdk。 >> when I used the ovs-dpdk with the bcm-NIC, there comes the error： >> >> here is the error in "/var/log/openvswitch/ovs-vswitchd.log" >> 2017-11-09T09:28:30.038Z|16773336|dpdk|INFO|EAL: PCI device :20:00.1 on >> NUMA socket 0 >> 2017-11-09T09:28:30.038Z|16773337|dpdk|INFO|EAL: probe driver: 14e4:168e >> net_bnx2x >> 2017-11-09T09:28:30.038Z|16773338|dpdk|WARN|EAL: Requested device >> :20:00.1 cannot be used >> 2017-11-09T09:28:30.038Z|16773339|dpdk|ERR|EAL: Driver cannot attach the >> device (:20:00.1) >> 2017-11-09T09:28:30.038Z|16773340|netdev_dpdk|WARN|Error attaching device >> ':20:00.1' to DPDK >> 2017-11-09T09:28:30.038Z|16773341|netdev|WARN|dpdk-eth2: could not set >> configuration (Invalid argument) > > >Looks like DPDK has the pmd enabled and has identified the device. >Did you bind the NIC to the VFIO driver before start OVS? > > >> And, my NIC firmware is : >> [root@node-4 ~]# ethtool -i eth2 >> driver: bnx2x >> version: 1.712.30-0 >> firmware-version: bc 7.0.49 >> expansion-rom-version: >> bus-info: :20:00.1 >> supports-statistics: yes >> supports-test: yes >> supports-eeprom-access: yes >> supports-register-dump: yes >> supports-priv-flags: yes >> >> >> Does the fm version not satisfies ? or some other reasons ? > >I don't know about FW versions. >fbl > > >> >> >> >> >> >> >> 在 2017-11-08 21:28:01，"Flavio Leitner" <f...@sysclose.org> 写道： >> >On Wed, 8 Nov 2017 11:15:00 +0800 (CST) >> >王嵘 <rong.w...@easystack.cn> wrote: >> > >> >> For now, I 'm using the "NetXtreme II BCM57810 10 Gigabit Ethernet 168e". >> >> Another question, I found ovs-dpdk can't bind this NIC. But I find >> >> there is the support code for 57810 in the DPDK Bnx2x. >> >> I'm puzzled. >> >> Can you tell me whether ovs-dpdk support this NIC? >> >> >> >> Thanks very much! >> > >> >You need to check that with your software provider. If you compiled >> >manually, then you need to check the options/config used to build DPDK. >> > >> >fbl >> > >> > >> >> 在 2017-11-08 09:11:25，"Ben Pfaff" <b...@ovn.org> 写道： >> >> >On Tue, Nov 07, 2017 at 03:49:06PM +0800, 王嵘 wrote: >> >> >> Hi, >> >> >> I'm using ovs-dpdk（ovs2.8/dpdk17.05.2), and I want to use the offload >> >> >> feature. But I dont know how to enable it? >> >> >> As is represented in the release note 2.8: >> >> >> >> >> >>- Addexperimental support for hardware offloading >> >> >> * HW offloading is disabled by default. >> >> >> >> >> >> * HW offloading is done through the TC interface. >> >> > >> >> >Do you have a supported NIC? This feature is currently for a particular >> >> >model of Mellanox NICs. >> > >> > >> > >> >-- >> >Flavio >> > > > > >-- >Flavio > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] hardware offloading in ovs-2.8
hi, I rpmbuild the ovs-dpdk by myself, and the "config/common_base" : CONFIG_RTE_LIBRTE_BNX2X_PMD=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=y CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=y CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC=y then ,I build the rpm of dpdk/dpdk-devel，and installed the 2 rpms to rpmbuild the ovs-dpdk。 when I used the ovs-dpdk with the bcm-NIC, there comes the error： here is the error in "/var/log/openvswitch/ovs-vswitchd.log" 2017-11-09T09:28:30.038Z|16773336|dpdk|INFO|EAL: PCI device :20:00.1 on NUMA socket 0 2017-11-09T09:28:30.038Z|16773337|dpdk|INFO|EAL: probe driver: 14e4:168e net_bnx2x 2017-11-09T09:28:30.038Z|16773338|dpdk|WARN|EAL: Requested device :20:00.1 cannot be used 2017-11-09T09:28:30.038Z|16773339|dpdk|ERR|EAL: Driver cannot attach the device (:20:00.1) 2017-11-09T09:28:30.038Z|16773340|netdev_dpdk|WARN|Error attaching device ':20:00.1' to DPDK 2017-11-09T09:28:30.038Z|16773341|netdev|WARN|dpdk-eth2: could not set configuration (Invalid argument) And, my NIC firmware is : [root@node-4 ~]# ethtool -i eth2 driver: bnx2x version: 1.712.30-0 firmware-version: bc 7.0.49 expansion-rom-version: bus-info: :20:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes Does the fm version not satisfies ? or some other reasons ? Thanks. 在 2017-11-08 21:28:01，"Flavio Leitner" <f...@sysclose.org> 写道： >On Wed, 8 Nov 2017 11:15:00 +0800 (CST) >王嵘 <rong.w...@easystack.cn> wrote: > >> For now, I 'm using the "NetXtreme II BCM57810 10 Gigabit Ethernet 168e". >> Another question, I found ovs-dpdk can't bind this NIC. But I find there >> is the support code for 57810 in the DPDK Bnx2x. >> I'm puzzled. >> Can you tell me whether ovs-dpdk support this NIC? >> >> Thanks very much! > >You need to check that with your software provider. If you compiled >manually, then you need to check the options/config used to build DPDK. > >fbl > > >> 在 2017-11-08 09:11:25，"Ben Pfaff" <b...@ovn.org> 写道： >> >On Tue, Nov 07, 2017 at 03:49:06PM +0800, 王嵘 wrote: >> >> Hi, >> >> I'm using ovs-dpdk（ovs2.8/dpdk17.05.2), and I want to use the offload >> >> feature. But I dont know how to enable it? >> >> As is represented in the release note 2.8: >> >> >> >>- Addexperimental support for hardware offloading >> >> * HW offloading is disabled by default. >> >> >> >> * HW offloading is done through the TC interface. >> > >> >Do you have a supported NIC? This feature is currently for a particular >> >model of Mellanox NICs. > > > >-- >Flavio > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] hardware offloading in ovs-2.8
For now, I 'm using the "NetXtreme II BCM57810 10 Gigabit Ethernet 168e". Another question, I found ovs-dpdk can't bind this NIC. But I find there is the support code for 57810 in the DPDK Bnx2x. I'm puzzled. Can you tell me whether ovs-dpdk support this NIC? Thanks very much! 在 2017-11-08 09:11:25，"Ben Pfaff" <b...@ovn.org> 写道： >On Tue, Nov 07, 2017 at 03:49:06PM +0800, 王嵘 wrote: >> Hi, >> I'm using ovs-dpdk（ovs2.8/dpdk17.05.2), and I want to use the offload >> feature. But I dont know how to enable it? >> As is represented in the release note 2.8: >> >>- Addexperimental support for hardware offloading >> * HW offloading is disabled by default. >> >> * HW offloading is done through the TC interface. > >Do you have a supported NIC? This feature is currently for a particular >model of Mellanox NICs. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] hardware offloading in ovs-2.8
Hi, I'm using ovs-dpdk（ovs2.8/dpdk17.05.2), and I want to use the offload feature. But I dont know how to enable it? As is represented in the release note 2.8: - Addexperimental support for hardware offloading * HW offloading is disabled by default. * HW offloading is done through the TC interface. thanks a lot. Rong.Wang ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] dpdk17.05 missing the rte_virtio_net.h
HI, I'm using dpdk17.05 and ovs2.7 for ovs-dpdk. And found a mistake. In the ovs lib/netdev-dpdk.c, there uses the header file "#include ", however, the dpdk17.05 has deleted the file. So, if it is a bug?. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
