Bug 1762119 - [RFE] Create a virtual PCI root complex per guest NUMA node when using q35
Summary: [RFE] Create a virtual PCI root complex per guest NUMA node when using q35
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: OSP DFG:Compute
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-16 01:06 UTC by smooney
Modified: 2024-10-01 16:21 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-05 14:42:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1626130 0 medium CLOSED [RFE] Auto-allocate PCIe route complex per NUMA node 2023-12-15 16:09:46 UTC
Red Hat Issue Tracker OSP-1589 0 None None None 2021-11-18 19:35:51 UTC
Red Hat Issue Tracker OSP-19166 0 None None None 2022-10-05 14:52:37 UTC

Description smooney 2019-10-16 01:06:54 UTC
Description of problem:

today if you have a multi numa node guest then all pci devices are assocated with virtual guest numa node0. this if the sriov device is associated with the virtual numa node 1 on the host this lead to cross qpi traffic forcine all acess
to the device to go though virtual numa node 0.

to prevent this nova should create at leat 1 pci root complex per virual guest
numa node and map the pci device to the numa local pci root complex.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Artom Lifshitz 2022-10-05 14:42:03 UTC
Starting with the Antelope upstream release, DFG:Compute is tracking its feature backlog in Jira. This feature request has been migrated to DFG:Compute’s new Jira backlog. The Jira tracker for this feature request can be found below. At the time of this writing, only Red Hat associates have access to the Jira tracker, but we are actively working on changing that as more and more of the OSP organization uses Jira for more things.

https://issues.redhat.com/browse/OSP-1589


Note You need to log in before you can comment on or make changes to this bug.