From: Jason Lunz <lunz@falooley.org>
To: netdev@oss.sgi.com
Subject: Re: [Patch 3/3 2.4] e1000: Update Documentation/networking/e1000.txt
Date: Fri, 15 Oct 2004 19:03:23 +0000 (UTC) [thread overview]
Message-ID: <ckp6tr$nrg$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.44.0410150507590.31227-100000@isotope.jf.intel.com
ganesh.venkatesan@intel.com said:
> + This sets the InterruptThrottleRate to 3000 interrupts/sec for the
> + first, second, and third instances of the driver. The range of 2000 to
> + 3000 interrupts per second works on a majority of systems and is a
> + good starting point, but the optimal value will be platform-specific.
> + If CPU utilization is not a concern, use RX_POLLING (NAPI) and default
> + driver settings.
I don't understand this bit. Isn't the point of NAPI to disable rx
interrupts entirely, and only gather as many frames from the driver as
CPU time permits? That's supposed to limit network-rx CPU usage, not
increase it as the above paragraph implies.
Jason
next prev parent reply other threads:[~2004-10-15 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 13:49 [Patch 3/3 2.4] e1000: Update Documentation/networking/e1000.txt Ganesh Venkatesan
2004-10-15 16:29 ` Jeff Garzik
2004-10-15 19:03 ` Jason Lunz [this message]
2004-10-15 19:20 ` akepner
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='ckp6tr$nrg$1@sea.gmane.org' \
--to=lunz@falooley.org \
--cc=netdev@oss.sgi.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).