This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 1865773 - [RFE] Use eBPF for RSS support on tun level
Summary: [RFE] Use eBPF for RSS support on tun level
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: ybendito
QA Contact: Lei Yang
URL:
Whiteboard:
Depends On:
Blocks: 1408902
TreeView+ depends on / blocked
 
Reported: 2020-08-04 06:51 UTC by ybendito
Modified: 2023-08-16 13:38 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 13:38:02 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-1297 0 None None None 2023-08-16 13:38:01 UTC

Description ybendito 2020-08-04 06:51:25 UTC 
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.
Comment 3 John Ferlan 2021-09-09 12:54:26 UTC 
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.
Comment 5 RHEL 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.
Comment 8 Lei Yang 2022-02-07 08:03:28 UTC 
Thanks for Yuri Update. Based on Comment 7, reopened this bug.
Comment 16 Laurent Vivier 2023-02-24 08:17:18 UTC 
Yuri,

what is the state of this BZ?

Thanks
Comment 17 ybendito 2023-02-26 09:33:58 UTC 
(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 18 RHEL 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.
Comment 19 Lei Yang 2023-08-10 07:29:36 UTC 
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
Comment 20 Lei Yang 2023-08-10 09:23:27 UTC 
(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 21 RHEL 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.
Note You need to log in before you can comment on or make changes to this bug.