From: Steve Wise <swise@opengridcomputing.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/2][RFC] Network Event Notifier Mechanism
Date: Thu, 22 Jun 2006 10:27:21 -0500 [thread overview]
Message-ID: <1150990041.3040.6.camel@stevo-desktop> (raw)
In-Reply-To: <1150984380.27156.4.camel@stevo-desktop>
On Thu, 2006-06-22 at 08:53 -0500, Steve Wise wrote:
> On Thu, 2006-06-22 at 01:57 -0700, David Miller wrote:
> > From: Steve Wise <swise@opengridcomputing.com>
> > Date: Wed, 21 Jun 2006 13:45:19 -0500
> >
> > > This patch implements a mechanism that allows interested clients to
> > > register for notification of certain network events.
> >
> > We have a generic network event notification facility called
> > netlink, please use it and extend it for your needs if necessary.
>
> I'll investigate this.
>
> Thanks,
The in-kernel Infiniband subsystem needs to know when certain events
happen. For example, if the mac address of a neighbour changes. Any
rdma devices that are using said neighbour need to be notified of the
change. You are asking that I extend the netlink facility (if
necessary) to provide this functionality.
Are you suggesting, then, that the Infiniband subsystem should create an
in-kernel NETLINK socket and obtain these events (and the pertinent
information) via the socket?
I'm still learning about netlink, but my understanding to date is that
its a way to pass events/commands between the kernel and user
applications. It perhaps seems overkill to use this mechanism for
kernel->kernel event notifications. That's why I started with notifier
blocks and added a netevent_notifier mechanism.
Any help is greatly appreciated. Sorry if I'm being dense...
Steve.
next prev parent reply other threads:[~2006-06-22 15:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 18:45 [PATCH 0/2][RFC] Network Event Notifier Mechanism Steve Wise
2006-06-21 18:45 ` [PATCH 1/2] " Steve Wise
2006-06-21 18:45 ` [PATCH 2/2] Core network changes to support network event notification Steve Wise
2006-06-21 19:08 ` [PATCH 0/2][RFC] Network Event Notifier Mechanism YOSHIFUJI Hideaki / 吉藤英明
2006-06-22 8:57 ` David Miller
2006-06-22 13:53 ` Steve Wise
2006-06-22 15:27 ` Steve Wise [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-06-21 19:48 Steve Wise
2006-06-21 20:40 ` David Miller
2006-06-22 22:11 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
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
2006-06-22 22:39 Caitlin Bestler
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=1150990041.3040.6.camel@stevo-desktop \
--to=swise@opengridcomputing.com \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.