netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, andy@greyhouse.net,
	sgruszka@redhat.com, stable@kernel.org
Subject: Re: [net-2.6 PATCH] ixgbe: fix automatic LRO/RSC settings for low latency
Date: Sun, 13 Jun 2010 18:21:10 -0700 (PDT)	[thread overview]
Message-ID: <20100613.182110.112601110.davem@davemloft.net> (raw)
In-Reply-To: <20100611224629.30958.22500.stgit@localhost.localdomain>

From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Fri, 11 Jun 2010 15:47:03 -0700

> From: Andy Gospodarek <andy@greyhouse.net>
> 
> This patch added to 2.6.34:
> 
> 	commit f8d1dcaf88bddc7f282722ec1fdddbcb06a72f18
> 	Author: Jesse Brandeburg <jesse.brandeburg@intel.com>
> 	Date:   Tue Apr 27 01:37:20 2010 +0000
> 
> 	    ixgbe: enable extremely low latency
> 
> introduced a feature where LRO (called RSC on the hardware) was disabled
> automatically when setting rx-usecs to 0 via ethtool.  Some might not
> like the fact that LRO was disabled automatically, but I'm fine with
> that.  What I don't like is that LRO/RSC is automatically enabled when
> rx-usecs is set >0 via ethtool.
> 
> This would certainly be a problem if the device was used for forwarding
> and it was determined that the low latency wasn't needed after the
> device was already forwarding.  I played around with saving the state of
> LRO in the driver, but it just didn't seem worthwhile and would require
> a small change to dev_disable_lro() that I did not like.
> 
> This patch simply leaves LRO disabled when setting rx-usecs >0 and
> requires that the user enable it again.  An extra informational message
> will also now appear in the log so users can understand why LRO isn't
> being enabled as they expect.
> 
> Inconsistency of LRO setting first noticed by Stanislaw Gruszka.
> 
> Signed-off-by: Andy Gospodarek <andy@greyhouse.net>
> CC: Stanislaw Gruszka <sgruszka@redhat.com>
> CC: stable@kernel.org
> Tested-by: Stephen Ko <stephen.s.ko@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

Applied.

      reply	other threads:[~2010-06-14  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 22:47 [net-2.6 PATCH] ixgbe: fix automatic LRO/RSC settings for low latency Jeff Kirsher
2010-06-14  1:21 ` David Miller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100613.182110.112601110.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andy@greyhouse.net \
    --cc=gospo@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    --cc=stable@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).