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.
Description of extension:
Currently in case of multiple vqueues in virtio-net the tun driver in the kernel is responsible for the receive steering. It maintains lookup table of TCPIP header hashes for transmitted packets, calculates hash for received packets and decides on RX queue to place the packet in. As now QEMU is aware of RSS settings of Windows quest, it can provide eBPF to tun driver to use it for faster decision of receive queue according to RSS settings.
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.
Comment 5RHEL Program Management
2022-02-04 07:27:13 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
(In reply to Laurent Vivier from comment #16)
> Yuri,
>
> what is the state of this BZ?
>
> Thanks
Support is added to QEMU, so the QEMU is able to use RSS with EBPF (i.e. also vhost=on) from the command line with root privileges.
Now we're submitting patches to QEMU and libvirt to make it possible to use this mode when qemu runs under libvirt.
Another patches are submitted to fix EBPF functionality with libbpf 1.1
Comment 18RHEL Program Management
2023-04-30 07:28:11 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Hello Yuri
Is there still plan to fix this problem on the rhel 9.3? If not, could you please help reset the ITR to 9.4.0? Thanks in advance.
Thanks
Lei
(In reply to Lei Yang from comment #19)
> Hello Yuri
>
> Is there still plan to fix this problem on the rhel 9.3? If not, could you
> please help reset the ITR to 9.4.0? Thanks in advance.
Because of QE noticed the following upstream patch looks like made to fix current bugs, but they has not been merge into upstream master. So from the QE's perspective this bug should be move to next release, please correct me if I'm wrong.
Commits ID:
ebpf: Added eBPF initialization by fds and map update.
virtio-net: Added property to load eBPF RSS with fds.
ebpf: Added declaration/initialization routines.
qmp: Added new command to retrieve eBPF blob.
>
> Thanks
> Lei
Comment 21RHEL Program Management
2023-08-15 15:25:07 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.