From: jamal <hadi@cyberus.ca>
To: Tim Hockin <thockin@hockin.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
<linux-kernel@vger.kernel.org>, <netdev@oss.sgi.com>
Subject: Re: rtnetlink interface state monitoring problems.
Date: Tue, 22 Oct 2002 23:17:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.30.0210222313050.24323-100000@shell.cyberus.ca> (raw)
In-Reply-To: <200210230144.g9N1iDx11822@www.hockin.org>
On Tue, 22 Oct 2002, Tim Hockin wrote:
> > If not, it probably time for someone to write a generic notification
> > scheme via netlink.
>
> How generic? I need to pay some attention to cleaning up the next version
> of the link-changes via netlink patch that was discussed last week or the
> week before.
The patch posted by Stefan seems good to me and ready to merge.
>
> What kind of generic are you thinking about? :)
>
netlink is a messaging system; so what i am thinking is creating
a event notifier for other devices other than network devices.
Something other non-network devices could use (eg bluetooth).
Given that netlink packetizes the data, this facilitates a distributed
control type of environment.
cheers,
jamal
next prev parent reply other threads:[~2002-10-23 3:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 11:18 David Woodhouse
2002-10-21 13:02 ` jamal
2002-10-21 18:57 ` David Woodhouse
2002-10-23 0:59 ` jamal
2002-10-23 1:44 ` Tim Hockin
2002-10-23 3:17 ` jamal [this message]
2002-10-23 19:42 ` Maksim (Max) Krasnyanskiy
2002-10-28 12:35 ` jamal
2002-10-23 19:41 ` Maksim (Max) Krasnyanskiy
2002-10-21 13:46 ` James Morris
2002-10-21 13:48 ` James Morris
2002-10-21 17:01 ` David S. Miller
2002-10-22 17:16 Jean Tourrilhes
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=Pine.GSO.4.30.0210222313050.24323-100000@shell.cyberus.ca \
--to=hadi@cyberus.ca \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=thockin@hockin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®