From owner-freebsd-net@FreeBSD.ORG  Thu May 20 15:14:13 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 88E1516A4CE
	for <freebsd-net@freebsd.org>; Thu, 20 May 2004 15:14:13 -0700 (PDT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0C4A243D45
	for <freebsd-net@freebsd.org>; Thu, 20 May 2004 15:14:13 -0700 (PDT)
	(envelope-from ddenissov@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72)
	id <KYKJYS45>; Thu, 20 May 2004 18:14:12 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337012C0D5A@mail.sandvine.com>
From: Dmitri Denissov <ddenissov@sandvine.com>
To: 'Julian Elischer' <julian@elischer.org>
Date: Thu, 20 May 2004 18:14:11 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2004 22:14:13 -0000

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.


> 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