All of lore.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Detecting link up
Date: Wed, 18 May 2005 23:06:32 +0800	[thread overview]
Message-ID: <2cd57c900505180806669beab@mail.gmail.com> (raw)
In-Reply-To: <20050518143712.GA21883@roonstrasse.net>

On 5/18/05, Max Kellermann <max@duempel.org> wrote:
> On 2005/05/18 13:40, Martin Zwickel <martin.zwickel@technotrend.de> wrote:
> > On Wed, 18 May 2005 11:35:12 +0100
> > Filipe Abrantes <fla@inescporto.pt> bubbled:
> > > I need to detect when an interface (wired ethernet) has link up/down.
> > > Is  there a system signal which is sent when this happens? What is the
> > > best  way to this programatically?
> >
> > mii-tool?
> 
> A thought on a related topic:
> 
> When a NIC driver knows that there is no link, why does it even try to
> transmit a packet? It could return immediately with an error code,
> without applications having to wait for a timeout.
> 
> (I had a quick peek at two drivers, and they don't check the link
> status)

An NIC driver doesn't know if there's other links or not. One NIC
driver is for one type of NIC.  And there's also interface lo.
-- 
Coywolf Qi Hunt
http://sosdg.org/~coywolf/

  parent reply	other threads:[~2005-05-18 15:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 10:35 Detecting link up Filipe Abrantes
2005-05-18 11:40 ` Martin Zwickel
2005-05-18 13:11   ` Vaibhav Nivargi
2005-05-18 13:57     ` Richard B. Johnson
2005-05-18 14:37   ` Max Kellermann
2005-05-18 15:00     ` Oliver Neukum
2005-05-18 15:06     ` Coywolf Qi Hunt [this message]
2005-05-18 15:11     ` Richard B. Johnson
2005-05-18 17:33   ` Michael Tokarev
2005-05-18 18:20 ` Stephen Hemminger
2005-05-18 22:20   ` Baruch Even

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=2cd57c900505180806669beab@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=coywolf@lovecn.org \
    --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.