| To: | "M. Warner Losh" <imp@bsdimp.com> |
|---|---|
| Subject: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port... |
| From: | David Daney <ddaney@avtrex.com> |
| Date: | Wed, 29 Jun 2005 19:33:28 -0700 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <20050629.195743.48512936.imp@bsdimp.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <42C1C6EA.5080709@avtrex.com> <42C34C4D.9020902@avtrex.com> <20050629.195743.48512936.imp@bsdimp.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mozilla Thunderbird 1.0.2-6 (X11/20050513) |
M. Warner Losh wrote: In message: <42C34C4D.9020902@avtrex.com> David Daney <ddaney@avtrex.com> writes: : Does anyone have any idea what would cause 1000mS delay? That's remarkably close to 1s. This often indicates that the transmit of your next packet is causing the receive buffer to empty. This is usually due to blocked interrupts, or a failure to enable interrupts. But I observe ever increasing counts for the device in /proc/interrupts. So the interrupts are working somewhat. David Daney |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port..., M. Warner Losh |
|---|---|
| Next by Date: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port..., M. Warner Losh |
| Previous by Thread: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port..., M. Warner Losh |
| Next by Thread: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port..., M. Warner Losh |
| Indexes: | [Date] [Thread] [Top] [All Lists] |