| To: | Harald Welte <laforge@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 2.6] natsemi.c NAPI |
| From: | Robert Olsson <Robert.Olsson@xxxxxxxxxxx> |
| Date: | Mon, 27 Sep 2004 12:30:17 +0200 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20040927091148.GF3236@sunbeam.de.gnumonks.org> |
| References: | <20040919163642.GC1307@sunbeam.de.gnumonks.org> <4155D781.8050700@colorfullife.com> <20040927091148.GF3236@sunbeam.de.gnumonks.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
> 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.
Cheers.
--ro
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 2.6] neighbour cache statistics like rt_stat, Harald Welte |
|---|---|
| Next by Date: | Re: [5/6]: Dynamic neigh hash table growth, Herbert Xu |
| Previous by Thread: | Re: [PATCH 2.6] natsemi.c NAPI, Harald Welte |
| Next by Thread: | Re: [PATCH 2.6] natsemi.c NAPI, Eric Lemoine |
| Indexes: | [Date] [Thread] [Top] [All Lists] |