Bug 1333195 - CPU isolated thread policy is not working properly.
Summary: CPU isolated thread policy is not working properly.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Eoghan Glynn
QA Contact: Prasanth Anbalagan
URL:
Whiteboard:
: 1333196 (view as bug list)
Depends On: 1332907 1333196
Blocks: 1277736
TreeView+ depends on / blocked
 
Reported: 2016-05-04 22:23 UTC by Stephen Gordon
Modified: 2019-09-09 16:43 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1332907
Environment:
Last Closed: 2016-05-06 11:26:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1578150 0 None None None 2016-05-04 22:23:11 UTC

Description Stephen Gordon 2016-05-04 22:23:11 UTC 
+++ This bug was initially created as a clone of Bug #1332907 +++

Description of problem:

Isolated thread policy is not working properly according to documentation.

Version-Release number of selected component (if applicable):


How reproducible:

Highly

Steps to Reproduce:

 Check https://bugs.launchpad.net/nova-solver-scheduler/+bug/1578150

Actual results:

 Sibling threads are used when the correspondent thread is ocuppied by an isolated vCPU.

Expected results:

 Have one thread per core unused.

Additional info:

 Check https://bugs.launchpad.net/nova-solver-scheduler/+bug/1578150
Comment 1 Stephen Gordon 2016-05-05 17:52:53 UTC 
*** Bug 1333196 has been marked as a duplicate of this bug. ***
Comment 2 Daniel Berrangé 2016-05-06 11:26:53 UTC 
Commented on the upstream bug - the reporter was trying to run guests with overcommit floating CPUs on the same host as guests with dedicated pinned CPUs. They should have been using host aggregates to separate these guests onto different hosts.
Note You need to log in before you can comment on or make changes to this bug.