Jeff Garzik wrote:
>
> "David S. Miller" wrote:
> >
> > Andrew Morton writes:
> > > It'd need to be callable from interrupt context - otherwise
> > > each device/driver which has link status change interrupts
> > > will need to implement some form of interrupt->process context
> > > trick.
> >
> > Well, we could make the netif_carrier_*() implementation do the
> > "interrupt->process context" trick.
> >
> > Jamal can feel free to post what he has.
>
> If we have any problems with context we can always use schedule_task()
Yep. With dev_hold() and dev_put() to avoid module removal
races. One would also have to be sure that the right things
happen if the interface is downed between the interrupt and
execution of the schedule_task() callback.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 15 2001 - 21:00:13 EST