From: Jeff Garzik <jeff@garzik.org>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
jesse.brandeburg@intel.com
Subject: Re: [PATCH 2/4] e1000: add module option to set transmit descriptor size
Date: Fri, 27 Jun 2008 01:10:37 -0400 [thread overview]
Message-ID: <4864764D.6070802@garzik.org> (raw)
In-Reply-To: <20080619211850.GD22981@gospo.rdu.redhat.com>
Andy Gospodarek wrote:
> This patch added the TxDescPower parameter to the e1000 module. This
> parameter represents the size-order of each transmit descriptor. The
> valid size for descriptors would be 2^7 (128) - 2^12 (4096) bytes each.
> As this value decreases one may want to consider increasing the
> TxDescriptors value to maintain the same amount of frame memory. This
> patch does not change the defaults for any particular hardware model, so
> this will not have an effect on existing users.
>
> The purpose of the patch is to address Tx Timeouts on 82545 and 82546
> chips that can show up during high-stress situations. Decreasing the
> transmit descriptor size can shorten the amount of time that will be
> spent DMAing frames to the hardware and can reduce the likely-hood that
> Tx Timeouts will occur.
>
> Signed-off-by: Andy Gospodarek <andy@greyhouse.net>
> ---
> drivers/net/e1000/e1000.h | 6 ++++++
> drivers/net/e1000/e1000_main.c | 12 ++----------
> drivers/net/e1000/e1000_param.c | 33 +++++++++++++++++++++++++++++++++++
> 3 files changed, 41 insertions(+), 10 deletions(-)
I don't see why a module parameter is needed. In practice, nobody will
ever think about this option, much less use it.
next prev parent reply other threads:[~2008-06-27 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 21:18 [PATCH 2/4] e1000: add module option to set transmit descriptor size Andy Gospodarek
2008-06-27 5:10 ` Jeff Garzik [this message]
2008-06-27 14:21 ` Arthur Jones
2008-06-27 14:55 ` Arthur Jones
2008-06-27 15:26 ` Andy Gospodarek
2008-06-27 14:39 ` Andy Gospodarek
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=4864764D.6070802@garzik.org \
--to=jeff@garzik.org \
--cc=andy@greyhouse.net \
--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).