From: Jesse Brandeburg
> On Mon, 23 Jan 2006, kus Kusche Klaus wrote:
> > Here are my results:
> >
> > If the watchdog doesn't get interrupted, preempted, or whatever,
> > it spends 340 us in its body:
> > * 303 us in the mii code
> > * 36 us in the f
From: John Ronciak
> Can we try a couple of things? 1) just comment out all the check for
> link code in the e100 driver and give that a try and 2) just comment
> out the update stats call and see if that works. These seem to be the
> differences and we need to know which one is causing the proble
From: Evgeniy Polyakov
> Just a hack:
>
> --- drivers/net/e100.c.1 2006-01-20 13:39:19.0 +0300
> +++ drivers/net/e100.c2006-01-20 14:15:40.0 +0300
> @@ -879,8 +879,8 @@
>
> writel((reg << 16) | (addr << 21) | dir | data,
> &nic->csr->mdi_ctrl);
>
> - for
From: Evgeniy Polyakov [mailto:[EMAIL PROTECTED]
> Each MDIO read can take upto 2 msecs (!) and at least 20
> usecs in e100,
> and this runs in timer handler.
> Concider attaching (only compile tested) patch which moves
> e100 watchdog
> into workqueue.
Tested the patch. Works and has the expec
From: Evgeniy Polyakov
> Each MDIO read can take upto 2 msecs (!) and at least 20
> usecs in e100,
> and this runs in timer handler.
> Concider attaching (only compile tested) patch which moves
> e100 watchdog
> into workqueue.
Hmmm, I don't think moving it around is worth the trouble
(neverthel
> From: John Ronciak
> During the watchdog the e100 driver reads all of the status registers
> from the actual hardware. There are 26 (worst case) register reads.
> There is also a spin lock for another check in the watchdog. It would
> still surprise me that all of this would take 500 usec. If
