| Summary: | Can't ping the vm then the dpdk function is enabled in the OpenStack infrastructure | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | liuwei <wliu> | ||||
| Component: | openvswitch-dpdk | Assignee: | Open vSwitch development team <ovs-team> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 9.0 (Mitaka) | CC: | amuller, atragler, brault, chrisw, fbaudin, fleitner, ichute, jniu, juhu, nyechiel, rkhan, sputhenp, srevivo, twilson, wliu, yrachman, zshi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-01-04 15:51:02 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: | |||||
| Attachments: |
|
||||||
|
Description
liuwei
2016-11-08 07:39:54 UTC
as per latest update, it can be resolved in test env after new ovs-dpdk version upgrade in new repo channel. Hu Jun will test this resolution next week and update the status. I validated that the issue has been resolved by upgrading ovs-dpdk to ovs-2.5 on site yesterday. but I think it has bug in openvswitch-dpdk-2.4.0-0.10346.git97bab959.2.el7.x86_64 and we need to find which bug it is at least, please trace this bug. I had the same exact issue and an upgrade to ovs-dpdk-2.5 seems to have fixed it. But L2 forwarding (testpmd) latency test is not showing good results. It gave me around 2500µs when the traffic is routed through VM, where as if directly connect the flows between the physical interfaces, I would get some where around 6µs. (In reply to Mohammed Salih from comment #10) > I had the same exact issue and an upgrade to ovs-dpdk-2.5 seems to have > fixed it. But L2 forwarding (testpmd) latency test is not showing good > results. It gave me around 2500µs when the traffic is routed through VM, > where as if directly connect the flows between the physical interfaces, I > would get some where around 6µs. By the way, I am using RT Kernel and KVM on host, with CPU pinned on 10-14 (node 1), humpages of 1G, 14 of them. VM is using 4 VCPU and 4 GB of RAM, uses uio_generic_pci for the interfaces. here is the testpmd options I've used. chrt -f 95 -l 1,2,3 --socket-mem 1024 -w 0000:00:03.0 -w 0000:00:04.0 -- -i --disable-hw-vlan --nb-cores=2 --auto-start Update: so we got the test cases working well with in the target of 30µs ( <13µs for 512B payload & <6µs for 64B payload). Thanks a lot Zenghui, for the suggestion to use openvswitch-2.5.0-14.git20160727.el7fdb.x86_64.rpm from rhel-7-fast-datapath-htb-rpms and for sharing the doc written by Andrew Theurer <atheurer>. Both helped to nail it down. Cheers ! Could you update the Status? Please checkout sos from upstream or get the RPM from RHEL7.3 and provide the sosreport from the affected systems to us after had reproduced the issue. |