From: Michael Renzmann <netdev@nospam.otaku42.de>
To: netdev@oss.sgi.com
Subject: Network driver behaviour when loosing link
Date: Sat, 21 May 2005 22:05:48 +0200 [thread overview]
Message-ID: <428F949C.8080707@otaku42.de> (raw)
Hi all.
I'm playing with a network driver and came across one thing I'd like to
ask something about.
Let's assume a driver detects a link status change (for example, the
link is dropped). I would have expected that the driver should signal
the change via netif_carrier_on/_off (if used at all) and tell the
kernel to stop/resume sending packets to the driver (via
netif_wake_queue/netif_stop_queue).
When checking several drivers I found some that call
netif_[wake|stop]_queue (e100, e1000), while others don't (natsemi, tg3).
Hence the question: what is the recommended behaviour in such a case? Is
it ok to call netif_[stop|wake]_queue? How about adjusting the
IFF_RUNNING flag accordingly? Is there any documentation available on
this topic?
Thanks in advance.
Bye, Mike
next reply other threads:[~2005-05-21 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 20:05 Michael Renzmann [this message]
2005-05-22 0:52 ` Network driver behaviour when loosing link Tommy Christensen
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=428F949C.8080707@otaku42.de \
--to=netdev@nospam.otaku42.de \
--cc=netdev@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).