| To: | tharbaugh@xxxxxxxx |
|---|---|
| Subject: | Re: [PATCH] abysmal e1000 performance (DITR) |
| From: | Jeff Garzik <jgarzik@xxxxxxxxx> |
| Date: | Thu, 26 Aug 2004 16:26:50 -0400 |
| Cc: | hadi@xxxxxxxxxx, "Venkatesan, Ganesh" <ganesh.venkatesan@xxxxxxxxx>, netdev@xxxxxxxxxxx, "Feldman, Scott" <scott.feldman@xxxxxxxxx>, "Brandeburg, Jesse" <jesse.brandeburg@xxxxxxxxx> |
| In-reply-to: | <1093550644.20769.130.camel@tubarao> |
| References: | <468F3FDA28AA87429AD807992E22D07E014CEF36@orsmsx408> <1093542930.1027.124.camel@xxxxxxxxxxxxxxxx> <1093550644.20769.130.camel@tubarao> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 |
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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: [PATCH] abysmal e1000 performance (DITR), Thayne Harbaugh |
|---|---|
| Next by Date: | Fw: [Bugme-new] [Bug 3278] New: Missing include statements, Andrew Morton |
| Previous by Thread: | RE: [PATCH] abysmal e1000 performance (DITR), Thayne Harbaugh |
| Next by Thread: | Re: [PATCH] abysmal e1000 performance (DITR), Thayne Harbaugh |
| Indexes: | [Date] [Thread] [Top] [All Lists] |