From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, jesse.brandeburg@intel.com
Subject: Re: [net-next-2.6 PATCH 2/2] e1000/e1000e: implement a simple interrupt moderation
Date: Thu, 06 May 2010 00:25:47 -0700 (PDT) [thread overview]
Message-ID: <20100506.002547.13753501.davem@davemloft.net> (raw)
In-Reply-To: <20100505082601.5956.29024.stgit@localhost.localdomain>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Wed, 05 May 2010 01:26:03 -0700
> From: Jesse Brandeburg <jesse.brandeburg@intel.com>
>
> Back before e1000-7.3.20, the e1000 driver had a simple algorithm that
> managed interrupt moderation. The driver was updated in 7.3.20 to
> have the new "adaptive" interrupt moderation but we have customer
> requests to redeploy the old way as an option. This patch adds the
> old functionality back. The new functionality can be enabled via
> module parameter or at runtime via ethtool.
> Module parameter: (InterruptThrottleRate=4) to use this new
> moderation method.
> Ethtool method: ethtool -C ethX rx-usecs 4
>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Applied.
next prev parent reply other threads:[~2010-05-06 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 8:25 [net-next-2.6 PATCH 1/2] e1000e: increase rx fifo size to 36K on 82574 and 82583 Jeff Kirsher
2010-05-05 8:26 ` [net-next-2.6 PATCH 2/2] e1000/e1000e: implement a simple interrupt moderation Jeff Kirsher
2010-05-06 7:25 ` David Miller [this message]
2010-05-06 7:25 ` [net-next-2.6 PATCH 1/2] e1000e: increase rx fifo size to 36K on 82574 and 82583 David Miller
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=20100506.002547.13753501.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.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).