From owner-freebsd-net Tue Nov 5 15: 9: 4 2002 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9970337B401; Tue, 5 Nov 2002 15:09:03 -0800 (PST) Received: from scl8owa02.int.exodus.net (scl8out02.exodus.net [66.35.230.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB3B543E88; Tue, 5 Nov 2002 15:09:02 -0800 (PST) (envelope-from Maksim.Yevmenkin@exodus.net) Received: from scl8owa01.int.exodus.net ([66.35.230.241]) by scl8owa02.int.exodus.net with Microsoft SMTPSVC(5.0.2195.5329); Tue, 5 Nov 2002 15:09:02 -0800 Received: from exodus.net ([206.220.227.147]) by scl8owa01.int.exodus.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.5329); Tue, 5 Nov 2002 15:09:02 -0800 Message-ID: <3DC84F87.D5CB9C1C@exodus.net> Date: Tue, 05 Nov 2002 15:08:55 -0800 From: Maksim Yevmenkin X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Archie Cobbs Cc: current@FreeBSD.ORG, net@FreeBSD.ORG, Julian Elischer Subject: Re: Netgraph and KQUEUE(2) References: <200211052231.gA5MVuJB040317@arch20m.dellroad.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 05 Nov 2002 23:09:02.0570 (UTC) FILETIME=[54AA74A0:01C28520] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Archie Cobbs wrote: > > Maksim Yevmenkin writes: > > I would like to get some feedback on the idea i have. > > Basically i would like Netgraph system to send kevents > > whenever something happens. For example: > > > > 1) node X of type Y was created/destroyed > > 2) hook X was connected/disconnected to/from node Y > > 3) Data passed via hook X > > 4) Node X got message Y > > This would be nice, but what does kqueue() really have to do with it? > > I.e., why not just allow the creation of a ng_monitor(4) (or whatever you > want to call it) node, which would send out event report messages to > whomever connected to it. common interface? reusing existing functionality? just open a Netgraph socket, register for events and away you go. and you are right ng_monitor (or whatever) is another way to do the same thing. thanks, max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message