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 773675 - Disable LRO for all NICs that have LRO enabled
Summary: Disable LRO for all NICs that have LRO enabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.3
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Mike Burns
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 772806
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-12 14:51 UTC by Chris Pelland
Modified: 2016-04-26 14:43 UTC (History)
29 users (show)

Fixed In Version: ovirt-node-2.0.2-0.14.3.git3eac501.el6_2.2
Doc Type: Bug Fix
Doc Text:
Previously, when an NIC was added to a bridge LRO would not automatically be disabled if a bond was also present. The use of a bond and a bridge on top of NICs using LRO presented serious performance degradation. This update ensures that LRO is disabled on all NICs, avoiding this performance degradation issue.
Clone Of:
Environment:
Last Closed: 2012-01-23 18:17:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0048 0 normal SHIPPED_LIVE rhev-hypervisor6 bug fix update 2012-01-23 23:15:49 UTC

Description Chris Pelland 2012-01-12 14:51:54 UTC 
This bug has been copied from bug #772806 and has been proposed
to be backported to 6.2 z-stream (EUS).
Comment 4 Mike Burns 2012-01-12 15:36:14 UTC 
See patch in bug 772806
Comment 6 Mike Burns 2012-01-12 17:41:56 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
A serious performance problem occurs when running using a bond and a bridge on top of NICs that use LRO.  LRO should get disabled automatically when the NIC is added to a bridge but this doesn't work right when there is a bond in between.  This patch disables LRO on all nics.
Comment 7 Stephen Gordon 2012-01-12 19:53:19 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-A serious performance problem occurs when running using a bond and a bridge on top of NICs that use LRO.  LRO should get disabled automatically when the NIC is added to a bridge but this doesn't work right when there is a bond in between.  This patch disables LRO on all nics.+Previously, when an NIC was added to a bridge LRO would not automatically be disabled if a bond was also present. The use of a bond and a bridge on top of NICs using LRO presented serious performance degradation. This update ensures that LRO is disabled on all NICs, avoiding this performance degradation issue.
Comment 8 Guohua Ouyang 2012-01-18 09:06:56 UTC 
On rhevh-6.2-20120117, LRO is disabled for all NICs now.

[root@unused admin]# cat /etc/modprobe.d/bnx2x.conf 
options bnx2x disable_tpa=1


Hi Mike, 
is above information is enough to close this bug? if not, could you ask customer to verify this bug in their environment?
Comment 9 Mike Burns 2012-01-18 13:00:04 UTC 
That should be sufficient.  Please confirm that it's disabled when nics are bonded as well.

Thanks
Comment 10 Andy Gospodarek 2012-01-18 13:28:38 UTC 
It will be sufficient for any bnx2x hardware, but will not be useful for other hardware that needs LRO disabled.
Comment 11 Mike Burns 2012-01-18 13:35:59 UTC 
(In reply to comment #10)
> It will be sufficient for any bnx2x hardware, but will not be useful for other
> hardware that needs LRO disabled.

Hi Andy,

This is what we're doing:

echo "options bnx2x disable_tpa=1" > /etc/modprobe.d/bnx2x.conf
echo "options mlx4_en num_lro=0" > /etc/modprobe.d/mlx4_en.conf
echo "options enic lro_disable=1" > /etc/modprobe.d/enic.conf
echo "options s2io lro=0" > /etc/modprobe.d/s2io.conf

Are we missing anything?  These were the options given to us back in the 5.x timeframe.
Comment 12 Mike Burns 2012-01-20 14:53:42 UTC 
Dropping needinfo, we're covering everything.
Comment 13 Ying Cui 2012-01-20 14:58:37 UTC 
According to comment 8, comment 9 and comment 12, I change the bug status to 'Verified.'
Comment 14 errata-xmlrpc 2012-01-23 18:17:25 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0048.html
Note You need to log in before you can comment on or make changes to this bug.