OVS n-handler-threads and n-handler-threads parameters are incoherent with hypervisor isolated core list
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Haresh |
Bug Description
Description
===========
All OpenStack and hypervisor services will run on the HostCpusList. The problem is that ovs-vswitchd is not aware of such partitioning, and is spawning many userland threads as it believes that he can run on all of the CPUs.
Steps to reproduce
==================
1) Deploy OVS. Observe the revalidator and handler threads
[heat-admin@
TID COMMAND
22031 ovs-vswitchd
22032 ovs-vswitchd
22034 ovs-vswitchd
22035 ovs-vswitchd
22036 ovs-vswitchd
22037 ovs-vswitchd
22038 dpdk_watchdog1
22046 urcu2
22066 ct_clean3
22739 pmd164
22740 pmd165
22741 pmd167
22742 pmd166
493539 handler613
493540 revalidator610 <<<<<<<
493541 revalidator611 <<<<<<<
493542 revalidator612 <<<<<<<
493543 revalidator614 <<<<<<<
Expected result
===============
Running on specified cores
Actual result
=============
Utilizing all available cores
Environment
===========
OVS with DPDK
Logs & Configs
sudo ovs-vsctl get Open_vSwitch . other_config:
sudo ovs-vsctl get Open_vSwitch . other_config:
==============
Changed in tripleo: | |
assignee: | nobody → Haresh (hakhande) |
status: | New → In Progress |
tags: | added: tripleo-heat-templates |
information type: | Public → Public Security |
information type: | Public Security → Public |
Changed in tripleo: | |
status: | Fix Released → In Progress |
Changed in tripleo: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. openstack. org/650627
Review: https:/