From: Stefan Rompf <srompf@isg.de>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: "David L. Parsley" <parsley@roanoke.edu>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: Interface operative status detection
Date: Tue, 12 Feb 2002 17:08:31 +0100 [thread overview]
Message-ID: <3C693DFF.E4C6F0AA@isg.de> (raw)
In-Reply-To: <3C498CC9.6FAED2AF@isg.de.suse.lists.linux.kernel> <p73g0525je4.fsf@oldwotan.suse.de> <3C692C1C.7090107@roanoke.edu> <3C693BA0.43104E47@nortelnetworks.com>
Hi,
> Now what I would *really* like to see would be a way to get asynchronous
> notification of userspace processes on link beat change. Of course, depending
> on NIC this would require an interrupt handler or a kernel thread periodically
> checking the link state, as well as some way to pass that information to the
> user (netlink socket, interrupt...not sure what the best would be).
I have already written code that sends a link state notification via
netlink socket, but still have to create the patches for 2.5, maybe
2.4ac and later 2.4. Just give me some more days, if you're working as a
software developer in your daily job, you are not always motivated to
run straight to your private computer afterworks, at least I am not ;-)
Stefan
next prev parent reply other threads:[~2002-02-12 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C498CC9.6FAED2AF@isg.de.suse.lists.linux.kernel>
2002-01-19 17:40 ` Interface operative status detection 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 [this message]
2002-01-19 15:12 Stefan Rompf
2002-01-19 15:29 ` Jeff Garzik
2002-01-19 18:34 ` Roberto Nibali
2002-02-08 10:16 ` Jeff Garzik
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=3C693DFF.E4C6F0AA@isg.de \
--to=srompf@isg.de \
--cc=ak@suse.de \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parsley@roanoke.edu \
/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