From mboxrd@z Thu Jan 1 00:00:00 1970 From: jamal Subject: Re: [PATCH 0/2][RFC] Network Event Notifier Mechanism Date: Thu, 22 Jun 2006 20:56:26 -0400 Message-ID: <1151024186.5099.46.camel@jzny2> References: <54AD0F12E08D1541B826BE97C98F99F15F55E2@NT-SJCA-0751.brcm.ad.broadcom.com> <20060622.155805.35017169.davem@davemloft.net> Reply-To: hadi@cyberus.ca Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, swise@opengridcomputing.com, caitlinb@broadcom.com Return-path: Received: from mx03.cybersurf.com ([209.197.145.106]:7093 "EHLO mx03.cybersurf.com") by vger.kernel.org with ESMTP id S1751108AbWFWA43 (ORCPT ); Thu, 22 Jun 2006 20:56:29 -0400 Received: from mail.cyberus.ca ([209.197.145.21]) by mx03.cybersurf.com with esmtp (Exim 4.30) id 1FtZyN-0001wQ-TM for netdev@vger.kernel.org; Thu, 22 Jun 2006 20:56:35 -0400 To: David Miller In-Reply-To: <20060622.155805.35017169.davem@davemloft.net> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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. > > There should be netlink counterparts for that stuff too, which > are generated by the notifier calls or similar. Sounds reasonable - so someone deciding to do this from user space would still be able to do so. cheers, jamal 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.