Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMaxime Coquelin
2017-12-12 14:02:45 UTC
Created attachment 1366669[details]
Guest XML example with one Virtio-net device per NUMA node
Description of problem:
Currently, in DPDK's Virtio PMD driver, the rings memory is allocated with SOCKET_ID_ANY parameter for NUMA affinity.
It turns out the rings memory will always be allocated on the same NUMA node of the CPU running the Virtio PMD probe, which is not always on the same NUMA node than the CPUs doing the device polling.
In case of big guests spanned on multiple hosts NUMA nodes (CPU, memory), the user may want to spread multiple Virtio devices on the different NUMA nodes, so that host and guest CPUs and memory used for one device are on a same NUMA node.
It is possible to set Virtio-pci device NUMA affinity by adding PCI eXpander Bridges (PXB) between the root port and the devices, but DPDK Virtio PMD does not use it to allocate the rings memory.
The goal of this ticket is to have Virtio PMD to allocate rings memory on the same node as the probed device.
Version-Release number of selected component (if applicable):
all DPDK version (up to v17.11)
How reproducible:
Steps to Reproduce:
Create a guest spanned on two host NUMA nodes and two Virtio device using vhost-user backend connected to OVS-DPDK .
The guest also create two NUMA nodes and assign memory and CPUs to it, and assign each Virtio device on a different NUMA node using PXB.
Once guest is booted, bind the two Virtio devices to vfio-pci, and start testpmd using these two devices.
On host side, check on which NUMA node the vhost ports are:
ovs-appctl dpif-netdev/pmd-rxq-show
Actual results:
The two vhost ports are on the same NUMA node
Expected results:
The two vhost ports are on different NUMA nodes
Additional info:
Please find in attachment an example of guest declaring 2 NUMA nodes pinned to 2 host NUMA nodes, with one virtio-net device on each node.
(In reply to Jean-Tsung Hsiao from comment #16)
> Hi Pei,
> This issue is on the VM side. Would you be able to take care of the bug
> verification?
> Thanks!
> Jean
Hi Jean,
OK, I'm taking it and will verify it soon.
Best regards,
Pei
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:3394
Created attachment 1366669 [details] Guest XML example with one Virtio-net device per NUMA node Description of problem: Currently, in DPDK's Virtio PMD driver, the rings memory is allocated with SOCKET_ID_ANY parameter for NUMA affinity. It turns out the rings memory will always be allocated on the same NUMA node of the CPU running the Virtio PMD probe, which is not always on the same NUMA node than the CPUs doing the device polling. In case of big guests spanned on multiple hosts NUMA nodes (CPU, memory), the user may want to spread multiple Virtio devices on the different NUMA nodes, so that host and guest CPUs and memory used for one device are on a same NUMA node. It is possible to set Virtio-pci device NUMA affinity by adding PCI eXpander Bridges (PXB) between the root port and the devices, but DPDK Virtio PMD does not use it to allocate the rings memory. The goal of this ticket is to have Virtio PMD to allocate rings memory on the same node as the probed device. Version-Release number of selected component (if applicable): all DPDK version (up to v17.11) How reproducible: Steps to Reproduce: Create a guest spanned on two host NUMA nodes and two Virtio device using vhost-user backend connected to OVS-DPDK . The guest also create two NUMA nodes and assign memory and CPUs to it, and assign each Virtio device on a different NUMA node using PXB. Once guest is booted, bind the two Virtio devices to vfio-pci, and start testpmd using these two devices. On host side, check on which NUMA node the vhost ports are: ovs-appctl dpif-netdev/pmd-rxq-show Actual results: The two vhost ports are on the same NUMA node Expected results: The two vhost ports are on different NUMA nodes Additional info: Please find in attachment an example of guest declaring 2 NUMA nodes pinned to 2 host NUMA nodes, with one virtio-net device on each node.