From: Eric Lemoine <eric.lemoine@gmail.com>
To: Robert Olsson <robert.olsson@data.slu.se>
Cc: Harald Welte <laforge@gnumonks.org>, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6] natsemi.c NAPI
Date: Mon, 27 Sep 2004 19:30:21 +0200 [thread overview]
Message-ID: <5cac192f04092710304a3d28b2@mail.gmail.com> (raw)
In-Reply-To: <16727.60345.857450.162620@robur.slu.se>
> > I think this overall problem can be solved if there was some per-device
> > variable that saves the IntrStatus until the NAPI callback gets
> > scheduled. What do you think? This wouldn't even need some locking,
> > since interrupts would be disabled before the field is updated, and not
> > re-enabled before the field is read by the NAPI callback?
> >
> > I was surprised that this solution is not suggested in the NAPI-HOWTO.txt, so I though there must be an error in my proposal...
> >
> > By using such a scheme, isn't it also possible to only offload RX into
> > the NAPI callback with clear-on-read devices?
> >
>
> e1000 used such technique before.If a remember correctly IntrStatus was
> saved in device priv struct.
That's also how it is done in current sungem.
--
Eric
next prev parent reply other threads:[~2004-09-27 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040919163642.GC1307@sunbeam.de.gnumonks.org>
[not found] ` <4155D781.8050700@colorfullife.com>
2004-09-27 9:11 ` [PATCH 2.6] natsemi.c NAPI Harald Welte
2004-09-27 10:30 ` Robert Olsson
2004-09-27 17:30 ` Eric Lemoine [this message]
[not found] ` <20040927081411.GC3236@sunbeam.de.gnumonks.org>
[not found] ` <1096343829.8660.107.camel@jzny.localdomain>
[not found] ` <4158E74C.7030709@colorfullife.com>
2004-09-28 10:39 ` jamal
2004-09-20 14:10 Harald Welte
2004-09-20 18:57 ` David S. Miller
2004-09-20 19:07 ` Jeff Garzik
2004-09-20 19:12 ` David S. Miller
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=5cac192f04092710304a3d28b2@mail.gmail.com \
--to=eric.lemoine@gmail.com \
--cc=laforge@gnumonks.org \
--cc=netdev@oss.sgi.com \
--cc=robert.olsson@data.slu.se \
/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).