From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 0/2][RFC] Network Event Notifier Mechanism Date: Thu, 22 Jun 2006 15:58:05 -0700 (PDT) Message-ID: <20060622.155805.35017169.davem@davemloft.net> References: <54AD0F12E08D1541B826BE97C98F99F15F55E2@NT-SJCA-0751.brcm.ad.broadcom.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hadi@cyberus.ca, swise@opengridcomputing.com, netdev@vger.kernel.org Return-path: Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:20970 "EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP id S1030441AbWFVW6R (ORCPT ); Thu, 22 Jun 2006 18:58:17 -0400 To: caitlinb@broadcom.com In-Reply-To: <54AD0F12E08D1541B826BE97C98F99F15F55E2@NT-SJCA-0751.brcm.ad.broadcom.com> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: "Caitlin Bestler" 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.