Re: [PATCH 2.6] natsemi.c NAPI

[Eric Lemoine <eric.lemoine@xxxxxxxxx>]

>  > 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