Bug 1561961
Summary: | [13] Optional NUMA affinity for PCI devices | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Lee Yarwood <lyarwood> | |
Component: | openstack-nova | Assignee: | Stephen Finucane <stephenfin> | |
Status: | CLOSED ERRATA | QA Contact: | James Parker <jparker> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 13.0 (Queens) | CC: | amcleod, amodi, dasmith, derli, djuran, egallen, eglynn, fbaudin, jhakimra, jniu, jparker, jraju, jschluet, kchamart, lyarwood, markmc, mbooth, mburns, mdeng, mschuppe, oblaut, panbalag, pchavva, rhos-maint, sbauza, sclewis, sgordon, slinaber, sputhenp, srevivo, stephenfin, supadhya, weiyongjun, yohmura, yrachman | |
Target Milestone: | z9 | Keywords: | FutureFeature, Patch, Triaged, ZStream | |
Target Release: | 13.0 (Queens) | |||
Hardware: | All | |||
OS: | Linux | |||
URL: | https://blueprints.launchpad.net/nova/+spec/share-pci-device-between-numa-nodes | |||
Whiteboard: | upstream_milestone_none upstream_definition_pending-approval upstream_status_unknown | |||
Fixed In Version: | openstack-nova-17.0.10-9.el7ost | Doc Type: | Enhancement | |
Doc Text: |
This release includes support for PCI device NUMA affinity policies. You can configure these policies as part of the `[pci]alias` configuration options. The following policies are supported:
- `required`
- `legacy`
- `preferred`
In all cases, strict NUMA affinity is provided if possible. The key difference between the policies is the amount of NUMA affinity you can sacrifice before failing to schedule.
You can use these policies to configure how strict your NUMA affinity is for each device, or more specifically, for each device alias. This is useful to ensure maximum resource utilization.
When you configure the 'preferred' policy for a PCI device, nova now utilizes CPUs on a different NUMA node from the NUMA node of the PCI device, if only a different node is available. This results in increased resource utilization with the downside of reduced performance for these instances.
|
Story Points: | --- | |
Clone Of: | 1446311 | |||
: | 1650606 (view as bug list) | Environment: | ||
Last Closed: | 2019-11-07 14:14:01 UTC | Type: | Feature Request | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1366208, 1446311, 1647536, 1757886, 1775575, 1775576, 1783354, 1791991 | |||
Bug Blocks: | 1188000, 1419231, 1419948, 1422243, 1427361, 1442136, 1650606 |
Comment 5
Lon Hohberger
2018-07-20 10:34:31 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3796 |