yahoo-eng-team team mailing list archive

[liuxiuli <liu.lixiu@xxxxxxxxxx>]

Public bug reported:

version:master
problem:
NUMATopologyFilter will not choose numa node which has sibling but not satisfies request and other vcpus satisfy request when cpu_thread_policy is prefer.

for example:
host has cpu info:
NUMA node0 CPU(s):     0-7,16-23
NUMA node1 CPU(s):     8-15,24-31

and vcpu_pin_set is 0,16-23, then the node 0's sibling is [0,16], and nod 1's sibling is [].
When I boot an instance with "hw:cpu_policy": "dedicated", "hw:cpu_thread_policy": "prefer" and 4 vcpus in flavor, NUMATopology would not choose node 0.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1599417

Title:
  NUMATopologyFilter will not choose numa node which has sibling but not
  request and other vcpus match request when only one node has sibling
  while host has two node when cpu_thread_policy is prefer.

Status in OpenStack Compute (nova):
  New

Bug description:
  version:master
  problem:
  NUMATopologyFilter will not choose numa node which has sibling but not satisfies request and other vcpus satisfy request when cpu_thread_policy is prefer.

  for example:
  host has cpu info:
  NUMA node0 CPU(s):     0-7,16-23
  NUMA node1 CPU(s):     8-15,24-31

  and vcpu_pin_set is 0,16-23, then the node 0's sibling is [0,16], and nod 1's sibling is [].
  When I boot an instance with "hw:cpu_policy": "dedicated", "hw:cpu_thread_policy": "prefer" and 4 vcpus in flavor, NUMATopology would not choose node 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1599417/+subscriptions