Messages in this thread | | | Date | Wed, 21 Aug 2002 12:45:37 -0400 | From | Chris Friesen <> | Subject | Re: mdelay causes BUG, please use udelay |
| |
"Martin J. Bligh" wrote:
> Whilst this sort of delay in interrupt context is undoubtedly bad > any way we do it, I'd question the context a little more before we > make a decision. This is called from e1000_reset_hw - are we likely > to ever actually call this except under initialisation?
I currently work on an embedded device and if we detect given network connection isn't working at all our first response is to switch to a working connection, then we reload the device driver for the non-working one. Since we may be doing other things at the same time, having this stall the machine for extended periods of time is definately not a good thing.
Chris
-- Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com - 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/
| |