On Fri, 2006-01-20 at 17:19 -0800, John Ronciak wrote: > On 1/20/06, Lee Revell <[EMAIL PROTECTED]> wrote: > > Seems like the important question is, why does e100 need a watchdog if > > eepro100 works fine without one? Isn't the point of a watchdog in this > > context to work around other bugs in the driver (or the hardware)? > There are a number of things that the watchdog in e100 does. It > checks link (up, down), reads the hardware stats, adjusts the adaptive > IFS and checks to 3 known hang conditions based on certain types of > the hardware. You might be able to get around without doing the > work-arounds (as long as you don't' see hangs happening with the > hardware being used) but the checking of the link and the stats are > probably needed.
Why don't these cause excessive scheduling delays in eepro100 then? Can't we just copy the eepro100 behavior? Lee - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
