Netdev List
 help / color / mirror / Atom feed
From: "Venkatesan, Ganesh" <ganesh.venkatesan@intel.com>
To: <tharbaugh@lnxi.com>, <netdev@oss.sgi.com>
Cc: "Feldman, Scott" <scott.feldman@intel.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Subject: RE: [PATCH] abysmal e1000 performance (DITR)
Date: Fri, 4 Jun 2004 08:44:08 -0700	[thread overview]
Message-ID: <468F3FDA28AA87429AD807992E22D07E014CEF36@orsmsx408> (raw)

Thayne:

We are studying the patch and will get back to you once we have a plan
to integrate it into the driver.

Thanks,
ganesh 
 
-------------------------------------------------
Ganesh Venkatesan
Network/Storage Division, Hillsboro, OR

-----Original Message-----
From: Thayne Harbaugh [mailto:tharbaugh@lnxi.com] 
Sent: Friday, June 04, 2004 7:20 AM
To: netdev@oss.sgi.com
Cc: Venkatesan, Ganesh; Feldman, Scott; Brandeburg, Jesse
Subject: Re: [PATCH] abysmal e1000 performance (DITR)

I have documented a serious performance problem with DITR in the e1000
driver.  I have sent a patch to the netdev list as well as CC'ed various
people at Intel.  There has been very little response.  I am wondering
who has reviewed the DITR performance problem and what the plans are for
fixing it.

-- 
Thayne Harbaugh
Linux Networx

             reply	other threads:[~2004-06-04 15:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 15:44 Venkatesan, Ganesh [this message]
2004-08-26 17:55 ` [PATCH] abysmal e1000 performance (DITR) jamal
2004-08-26 20:04   ` Thayne Harbaugh
2004-08-26 20:26     ` Jeff Garzik
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=468F3FDA28AA87429AD807992E22D07E014CEF36@orsmsx408 \
    --to=ganesh.venkatesan@intel.com \
    --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