Bug 1304507
Summary: | A multi-queue vhostuser failed to start testpmd due to port start failure | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jean-Tsung Hsiao <jhsiao> |
Component: | openvswitch-dpdk | Assignee: | Flavio Leitner <fleitner> |
Status: | CLOSED WORKSFORME | QA Contact: | Jean-Tsung Hsiao <jhsiao> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.3 | CC: | aloughla, fleitner, jhsiao, kzhang, rcain |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-12 14:36:10 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jean-Tsung Hsiao
2016-02-03 20:55:29 UTC
Same here. I could reproduce this issue with vhost MQ (not vhost-user) Could you please confirm if you also can reproduce? If so, that means MQ is broken for testpmd and virtio and is not related to vhost-user MQ implementation in the host. Thanks, fbl (In reply to Flavio Leitner from comment #2) > Same here. > I could reproduce this issue with vhost MQ (not vhost-user) > Could you please confirm if you also can reproduce? There is no such issue with vhostuser. NOTE: I am using exactly the same host OVS vhostuser configuration. The only change is removing the <driver queues='4'> section from the xml file. > > If so, that means MQ is broken for testpmd and virtio and is not related to > vhost-user MQ implementation in the host. Agree. > > Thanks, > fbl > 3.Run "ethtool -L eth0 combined 4;ethtool -L eth1 combined 4" Please skip that command as for DPDK we don't need ethtool, but it might change the driver in such way that DPDK might not expect. > testpmd -l 0,1,2,3 -n 1 -d /usr/lib64/librte_pmd_virtio.so \ Please also add the number of descriptions which is needed for virtio: --rxd=256 --txd=256 > Version-Release number of selected component (if applicable): > * On vhostuser guest > [root@localhost jhsiao]# rpm -qa | grep dpdk > dpdk-tools-2.1.0-5.el7.x86_64 > dpdk-2.1.0-5.el7.x86_64 Please update to DPDK 2.2.0 which supports multiple queue. We don't support DPDK 2.1.0 anymore. testpmd has a very simple way to allocate CPUs for queues which is literally one core for each queue. So, for 4 queues doing forwarding between 2 devices you actually need 8 cores. (There is a plan to improve this algorithm) Thanks, (In reply to Flavio Leitner from comment #4) > > 3.Run "ethtool -L eth0 combined 4;ethtool -L eth1 combined 4" Yes, this is not needed for running testpmd. > > Please skip that command as for DPDK we don't need ethtool, but it might > change the driver in such way that DPDK might not expect. > > > testpmd -l 0,1,2,3 -n 1 -d /usr/lib64/librte_pmd_virtio.so \ > > Please also add the number of descriptions which is needed for virtio: > --rxd=256 --txd=256 already added. > > > Version-Release number of selected component (if applicable): > > * On vhostuser guest > > [root@localhost jhsiao]# rpm -qa | grep dpdk > > dpdk-tools-2.1.0-5.el7.x86_64 > > dpdk-2.1.0-5.el7.x86_64 > > Please update to DPDK 2.2.0 which supports multiple queue. By replacing 2.1.0 by 2.2.0 this bug went away. I,ll close this BZ. > We don't support DPDK 2.1.0 anymore. > > testpmd has a very simple way to allocate CPUs for queues which is literally > one core for each queue. So, for 4 queues doing forwarding between 2 > devices you actually need 8 cores. (There is a plan to improve this > algorithm) > > Thanks, |