From: Jeff Garzik <jgarzik@pobox.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
Netdev <netdev@oss.sgi.com>, Ayaz Abdulla <AAbdulla@nvidia.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [patch] forcedeth: add support for interrupt mitigation
Date: Fri, 21 Oct 2005 17:07:13 -0400 [thread overview]
Message-ID: <43595881.3030809@pobox.com> (raw)
In-Reply-To: <20051021202908.GA18966@electric-eye.fr.zoreil.com>
FWIW the ideal is to implement both NAPI -and- hardware interrupt
mitigation.
Jeff
next prev parent reply other threads:[~2005-10-21 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 18:13 [patch] forcedeth: add support for interrupt mitigation Manfred Spraul
2005-10-21 20:29 ` Francois Romieu
2005-10-21 20:42 ` John W. Linville
2005-10-21 21:07 ` Jeff Garzik [this message]
2005-10-21 21:33 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-10-21 21:10 Ayaz Abdulla
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=43595881.3030809@pobox.com \
--to=jgarzik@pobox.com \
--cc=AAbdulla@nvidia.com \
--cc=linville@tuxdriver.com \
--cc=manfred@colorfullife.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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).