From: Robert Olsson <Robert.Olsson@data.slu.se>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: "Jeff Garzik" <jgarzik@pobox.com>,
"Samuel Flory" <sflory@rackable.com>, <netdev@oss.sgi.com>
Subject: RE: More 2.4.22pre10 ACPI breakage
Date: Mon, 11 Aug 2003 00:22:50 +0200 [thread overview]
Message-ID: <16182.50618.69504.611254@robur.slu.se> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E01022292E1@orsmsx402.jf.intel.com>
Feldman, Scott writes:
> NAPI always-poll mode...that would be fun to play with...
> Is this what you're thinking: 1) block any place the driver enables
> interrupts so interrupts stay disabled, 2) ignore netif_rx_complete so
> we stay in polling mode, 3) ignore return code from netdev->poll.
>
> For 1), the driver needs some way to know that we're in always-poll-mode
> so enabling interrupts is a nop.
>
I will work but I doubt the usefulness of it as we spin aggressively even
when there low or no load. This as NAPI tries to serve your dev->poll
fastest possible given the fairness conditions are met.
I could think of a variant...
As dev->poll is callback we could possibly schedule (and delay) via a timer
or something with in turn does the the schedule dev->poll for us. We have
to return netif_rx_complete and have RX-buffers etc.
> Just thinking out loud - haven't tried any of this.
Same here... :-)
Cheers.
--ro
next prev parent reply other threads:[~2003-08-10 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 22:34 More 2.4.22pre10 ACPI breakage Feldman, Scott
2003-08-10 22:22 ` Robert Olsson [this message]
[not found] <C6F5CF431189FA4CBAEC9E7DD5441E01022292CD@orsmsx402.jf.intel.com>
2003-08-06 2:58 ` Jeff Garzik
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=16182.50618.69504.611254@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.com \
--cc=sflory@rackable.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).