From: Steve Wise <swise@opengridcomputing.com>
To: hadi@cyberus.ca
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, caitlinb@broadcom.com
Subject: Re: [PATCH 0/2][RFC] Network Event Notifier Mechanism
Date: Fri, 23 Jun 2006 08:24:43 -0500 [thread overview]
Message-ID: <1151069083.7808.19.camel@stevo-desktop> (raw)
In-Reply-To: <1151024186.5099.46.camel@jzny2>
On Thu, 2006-06-22 at 20:56 -0400, jamal wrote:
> On Thu, 2006-22-06 at 15:58 -0700, David Miller wrote:
>
> > Anyways, we can create normal notifiers for neighbour and route
> > events just like we have for network device stuff.
> >
So did you agree with a new notifier head for these events as in my
original patch? Or do you think I should add these to the netdev
notifier?
> > There should be netlink counterparts for that stuff too, which
> > are generated by the notifier calls or similar.
>
Ok.
> PS:- I do think what they need is to hear route cache generation
> as opposed to ARP+FIB updates; but lets wait and see how clever
> the patches would look.
>
Based on what I undestand from this thread, I should keep a notifier
block for these events and integrate that so the events also get passed
up to user space via netlink.
Can you expand on your statement above? If hooking route cache
generation gets all the events I described, then I'd like to use that.
I'm still learning the Linux routing subsystem. Any help would be
GREAT!
Thanks,
Steve.
next prev parent reply other threads:[~2006-06-23 13:24 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
2006-06-23 0:56 ` jamal
2006-06-23 13:24 ` Steve Wise [this message]
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=1151069083.7808.19.camel@stevo-desktop \
--to=swise@opengridcomputing.com \
--cc=caitlinb@broadcom.com \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=netdev@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 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).