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.
Bug 1949127 - [RFE] support the 'queue_id' bond option
Summary: [RFE] support the 'queue_id' bond option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Gris Ge
QA Contact: Matej Berezny
Jaroslav Klech
URL:
Whiteboard:
Depends On:
Blocks: 1951910
TreeView+ depends on / blocked
 
Reported: 2021-04-13 13:35 UTC by Beniamino Galvani
Modified: 2022-05-17 16:07 UTC (History)
14 users (show)

Fixed In Version: NetworkManager-1.34.0-0.1.el9
Doc Type: Enhancement
Doc Text:
.NetworkManager allows to change `queue_id` of bond port NetworkManager ports in a bond now supports the `queue_id` parameter. Assuming `eth1` is a port of bond interface, you can enable `queue_id` for a bond port with: [literal,subs="quotes"] ---- # nmcli connection modify eth1 bond-port.queue-id 1 # nmcli connection up eth1 ---- Any network interface that needs to use this option should configure it with multiple calls until proper priorities are set for all interfaces. For more information, see `/usr/share/docs/kernel-doc-_<version>/Documentation/networking/bonding.rst` file that is provided by the `kernel-doc` package.
Clone Of:
Environment:
Last Closed: 2022-05-17 15:48:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2022:3915 0 None None None 2022-05-17 15:48:28 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 829 0 None None None 2021-09-06 09:15:38 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 952 0 None None None 2021-08-27 04:02:04 UTC

Description Beniamino Galvani 2021-04-13 13:35:37 UTC
NM should support the 'queue_id' bond option. From [1]:

  The queue_id for a slave can be set using the command::

	  # echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id

  Any interface that needs a queue_id set should set it with multiple calls
  like the one above until proper priorities are set for all interfaces.  On
  distributions that allow configuration via initscripts, multiple 'queue_id'
  arguments can be added to BONDING_OPTS to set all needed slave queues.

[1] https://www.kernel.org/doc/Documentation/networking/bonding.rst

Comment 7 Gris Ge 2021-06-22 07:55:29 UTC
The `queue_id` information is exposed by kernel netlink at the bond port level, not the bond itself.

For the new design in NetworkManager, I would suggest we do the similar thing like `NM.SettingBridgePort`.

Comment 8 Gris Ge 2021-08-27 04:02:31 UTC
Upstream patch merged at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/952

Comment 15 Gris Ge 2021-11-01 08:40:24 UTC
The document is incorrect.

With NetworkManager shipped by this bug, user could use NetworkManager instead of sysfs to change the queue_id of bond port.
(assuming eth1 is a port of bond interface).

    sudo nmcli c modify eth1 bond-port.queue-id 1
    sudo nmcli c up eth1

Comment 16 Jaroslav Klech 2021-11-03 14:23:02 UTC
(In reply to Gris Ge from comment #15)
> The document is incorrect.
> 
> With NetworkManager shipped by this bug, user could use NetworkManager
> instead of sysfs to change the queue_id of bond port.
> (assuming eth1 is a port of bond interface).
> 
>     sudo nmcli c modify eth1 bond-port.queue-id 1
>     sudo nmcli c up eth1

Thanks Gris,

I assume only the heading was incorrect. So I fixed that and hope the rest remains OK. If not, feel free to let me know what parts should i updated.

Thanks,
Jaroslav

Comment 17 Gris Ge 2021-11-11 07:13:17 UTC
Document looks good to me now. Thanks!

Comment 18 Gris Ge 2021-11-11 07:19:46 UTC
https://www.kernel.org/doc/Documentation/networking/bonding.txt
The section 3.6 Overriding Configuration for Special Cases explained the detail usage of this `queue_id` of bond port.

Comment 23 errata-xmlrpc 2022-05-17 15:48:15 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 (new packages: NetworkManager), 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-2022:3915


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