public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Stefan Rompf <srompf@isg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interface operative status detection
Date: Sat, 19 Jan 2002 10:29:56 -0500	[thread overview]
Message-ID: <3C4990F4.EF7A5B13@mandrakesoft.com> (raw)
In-Reply-To: <3C498CC9.6FAED2AF@isg.de>

Stefan Rompf wrote:
> So what about the following idea: The network interface drivers use the
> netif_carrier_on() and netif_carrier_off() functions to update their
> interface card status (a bunch of drivers already do). To get this
> information forwarded to user mode via netlink socket, we use a kernel
> thread that goes through the device list, and everytime IFF_RUNNING
> and netif_carrier_ok() differ, IFF_RUNNING is updated and a message is
> sent via netlink.

In fact, that's the 2.5 plan -- send link up/down notifications via
netlink.  If you provide a patch, more the better.

For 2.4, you'll need to poll ETHTOOL_GLINK, assuming that the driver
supports ethtool.

In any case, your tulip patch looks pretty good on first review.  I'll
likely apply it to 2.4 and 2.5 after testing and further review.

	Jeff



-- 
Jeff Garzik      | Alternate titles for LOTR:
Building 1024    | Fast Times at Uruk-Hai
MandrakeSoft     | The Took, the Elf, His Daughter and Her Lover
                 | Samwise Gamgee: International Hobbit of Mystery

  reply	other threads:[~2002-01-19 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-19 15:12 Interface operative status detection Stefan Rompf
2002-01-19 15:29 ` Jeff Garzik [this message]
2002-01-19 18:34 ` Roberto Nibali
2002-02-08 10:16 ` Jeff Garzik
     [not found] <3C498CC9.6FAED2AF@isg.de.suse.lists.linux.kernel>
2002-01-19 17:40 ` Andi Kleen
2002-01-20  0:51   ` Stefan Rompf
2002-02-12 14:52   ` David L. Parsley
2002-02-12 15:58     ` Chris Friesen
2002-02-12 16:08       ` Stefan Rompf

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=3C4990F4.EF7A5B13@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srompf@isg.de \
    /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