From owner-freebsd-net@FreeBSD.ORG Thu May 20 15:21:28 2004 Return-Path: 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 C862016A4CE for ; Thu, 20 May 2004 15:21:28 -0700 (PDT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 880A143D41 for ; Thu, 20 May 2004 15:21:28 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc13) with ESMTP id <2004052022212701600aopm5e>; Thu, 20 May 2004 22:21:27 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA75602; Thu, 20 May 2004 15:21:25 -0700 (PDT) Date: Thu, 20 May 2004 15:21:24 -0700 (PDT) From: Julian Elischer To: Dmitri Denissov In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: RE: protecting netgraph calls from outside of the network context X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2004 22:21:28 -0000 On Thu, 20 May 2004, Dmitri Denissov wrote: > This is kind of a bridge, connected to ng_ether interface nodes. > Sometimes it queues received packets and later /on a timer call or a call > from the user space/ > it re-injects the packets using ng_send_data. > reinjects it to where? > > > From: Julian Elischer [mailto:julian@elischer.org] > > Sent: Thursday, May 20, 2004 5:34 PM > > > > > > Ha! funny you should ask that exactly now.. > > I was just discussing this with Robert Watson.. > > > > The answer is "it depends on what you want to do". > > > > What DO you want to do and what does your node do? > > netgraph has internal locking in 5.x that you need to > > interact with but it should be pretty transparrent > > depending on what you are doing.. > > > > > > On Thu, 20 May 2004, Dmitri Denissov wrote: > > > > > Hi, > > > > > > Currently netgraph code uses splnet/splx to protect timeout calls. > > > This doesn't work with 5.2 SMP kernel. What is the proper method > > > here for a custom netgraph node? Is the Giant lock only the way? > > > > > > Thanks > > > > > > -- > > > Dmitri >