From: David Miller <davem@davemloft.net>
To: caitlinb@broadcom.com
Cc: hadi@cyberus.ca, swise@opengridcomputing.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/2][RFC] Network Event Notifier Mechanism
Date: Thu, 22 Jun 2006 15:58:05 -0700 (PDT) [thread overview]
Message-ID: <20060622.155805.35017169.davem@davemloft.net> (raw)
In-Reply-To: <54AD0F12E08D1541B826BE97C98F99F15F55E2@NT-SJCA-0751.brcm.ad.broadcom.com>
From: "Caitlin Bestler" <caitlinb@broadcom.com>
Date: Thu, 22 Jun 2006 15:11:27 -0700
> I don't have any strong opinion on the best mechanism
> for implementing these subscriptions, but having correct
> consistent networking behaviour depend on a user-mode
> relay strikes me as odd.
Never heard of a routing daemon? That all works in userspace.
Anyways, we can create normal notifiers for neighbour and route
events just like we have for network device stuff.
There should be netlink counterparts for that stuff too, which
are generated by the notifier calls or similar.
next prev parent reply other threads:[~2006-06-22 22:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 22:11 [PATCH 0/2][RFC] Network Event Notifier Mechanism Caitlin Bestler
2006-06-22 22:21 ` jamal
2006-06-22 22:58 ` David Miller [this message]
2006-06-23 0:56 ` jamal
2006-06-23 13:24 ` Steve Wise
2006-06-23 19:57 ` David Miller
2006-06-23 20:12 ` Steve Wise
2006-06-24 14:30 ` jamal
2006-06-26 14:34 ` Steve Wise
2006-06-27 12:44 ` jamal
-- strict thread matches above, loose matches on Subject: below --
2006-06-22 22:39 Caitlin Bestler
2006-06-21 18:45 Steve Wise
2006-06-21 19:08 ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-22 8:57 ` David Miller
2006-06-22 13:53 ` Steve Wise
2006-06-22 15:27 ` Steve Wise
2006-06-22 19:43 ` jamal
2006-06-22 20:18 ` Steve Wise
2006-06-22 20:36 ` jamal
2006-06-22 20:58 ` Steve Wise
2006-06-22 22:14 ` jamal
2006-06-23 13:11 ` Steve Wise
2006-06-22 20:40 ` Steve Wise
2006-06-22 20:56 ` jamal
2006-06-23 13:17 ` Steve Wise
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=20060622.155805.35017169.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=caitlinb@broadcom.com \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.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).