From: Ian Kumlien <pomac@vapor.com>
To: linux-kernel@vger.kernel.org
Subject: [help] Netdev watchdog code?
Date: Sun, 27 Jun 2004 02:42:02 +0200 [thread overview]
Message-ID: <1088296922.23713.45.camel@big> (raw)
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
Hi,
Do i understand this right?
Netdev watchdog can only be called when netif_stop_queue(...) has been
called. From what i gather in b44.c it's only called when the send queue
is full, yet it can trigger on a common dhcp request.
(where netif_queue_stopped(...) should return false, and thus the
watchdog shouldn't run at all)
As it is now, i can't understand how i can get watchdog timeouts since
the queue would have to be filled. On a 100mbit fdup link it shouldn't
delay that long not even if you use UDP packets (like nfs, I've even
seen it trigger with ftp now).
Anyways, Doing bio-timing based on the text output, it should work.
And, the current vanila kernel.org kernel doesn't work for me, as i have
stated numerous times and received no feedback.
PS, CC, not in list.
DS.
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-06-27 0:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1088296922.23713.45.camel@big \
--to=pomac@vapor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.