From: Jeff Garzik <jgarzik@pobox.com>
To: tharbaugh@lnxi.com
Cc: hadi@cyberus.ca, "Venkatesan,
Ganesh" <ganesh.venkatesan@intel.com>,
netdev@oss.sgi.com, "Feldman, Scott" <scott.feldman@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Subject: Re: [PATCH] abysmal e1000 performance (DITR)
Date: Thu, 26 Aug 2004 16:26:50 -0400 [thread overview]
Message-ID: <412E478A.2000806@pobox.com> (raw)
In-Reply-To: <1093550644.20769.130.camel@tubarao>
Thayne Harbaugh wrote:
> On Thu, 2004-08-26 at 13:55 -0400, jamal wrote:
>
>>Ganesh,
>>
>>Can you please make this feature off by default and perhaps
>>accesible via ethtool for peopel who want to turn it on.
>>I just wasted a few hours and was bitten by this performance-wise.
>>Please consider disabling it.
>
>
> This is a *horrible* problem. Even though it's fixable by passing a
> module parameter, the default bites those that *know* about it. We have
> had customers bitten by this and customers that have insisted in
> swapping all the NICs in a cluster to Broadcom TG3 NICs.
>
> It's a black eye for Intel and a loss of business - that's the opinion
> of our customers.
If it's so bad we should disable it by default, either via the module
parameter or via a kernel CONFIG_xxx option.
Jeff
next prev parent reply other threads:[~2004-08-26 20:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 15:44 [PATCH] abysmal e1000 performance (DITR) Venkatesan, Ganesh
2004-08-26 17:55 ` jamal
2004-08-26 20:04 ` Thayne Harbaugh
2004-08-26 20:26 ` Jeff Garzik [this message]
2004-08-26 21:28 ` Thayne Harbaugh
2004-08-28 22:58 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-08-27 22:41 Ronciak, John
2004-08-30 17:06 ` Thayne Harbaugh
2004-08-27 21:49 Ronciak, John
2004-08-27 22:05 ` Thayne Harbaugh
2004-06-01 23:05 Thayne Harbaugh
2004-06-04 14:20 ` Thayne Harbaugh
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=412E478A.2000806@pobox.com \
--to=jgarzik@pobox.com \
--cc=ganesh.venkatesan@intel.com \
--cc=hadi@cyberus.ca \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.com \
--cc=tharbaugh@lnxi.com \
/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).