From owner-freebsd-arch@FreeBSD.ORG Mon Sep 6 09:45:38 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3007916A4CE for ; Mon, 6 Sep 2004 09:45:38 +0000 (GMT) Received: from n33.kp.t-systems-sfr.com (n33.kp.t-systems-sfr.com [129.247.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68EBD43D6D for ; Mon, 6 Sep 2004 09:45:37 +0000 (GMT) (envelope-from harti@freebsd.org) Received: from n81.sp.op.dlr.de (n81g.sp.op.dlr.de [129.247.163.1]) i869jL2362950; Mon, 6 Sep 2004 11:45:21 +0200 Received: from zeus.nt.op.dlr.de (zeus.nt.op.dlr.de [129.247.173.3]) i869jKI109740; Mon, 6 Sep 2004 11:45:20 +0200 Received: from beagle.kn.op.dlr.de (opkndnwsbsd178 [129.247.173.178]) by zeus.nt.op.dlr.de (8.11.7+Sun/8.9.1) with ESMTP id i869j5e21175; Mon, 6 Sep 2004 11:45:15 +0200 (MET DST) Date: Mon, 6 Sep 2004 11:45:06 +0200 (CEST) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: "Bjoern A. Zeeb" In-Reply-To: Message-ID: <20040906113737.X16723@beagle.kn.op.dlr.de> References: <4134DF35.7070605@freebsd.org><4134E4B6.2030409@elischer.org> <4134FCAE.7374599A@freebsd.org> <4134FF74.4010105@freebsd.org> <4135051E.2070007@elischer.org> <4135118A.5030807@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-arch@freebsd.org Subject: Re: netgraph locking / performance [was: ... AOE] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2004 09:45:38 -0000 On Mon, 6 Sep 2004, Bjoern A. Zeeb wrote: BAZ>On Tue, 31 Aug 2004, Scott Long wrote: BAZ> BAZ>Hi, BAZ> BAZ>> My employer has done extensive profiling of packet delivery through BAZ>> netgraph. While the locking of the netgraph framework is definitely BAZ>> correct, it's not terribly efficient and leads to a good deal of BAZ>> latency. We are looking at various proposals on how to address this. BAZ>> This isn't a criticism of you or Netgraph, just a set 'real-life' BAZ>> observations under very high load (bridging and packet inspection on BAZ>> 4 GigE links simultaneously qualifies as high load =-) BAZ> BAZ>could please explain a bit more / give some numbers ? Or are there BAZ>any published results ? What do you mean by 'packet inspection' ? That would also interest me. I did measurements with my satellite link simulator (a netgraph node) and got a couple of 100usec latency when pushing 150k ATM cells through the node (each cell counting as a packet). including the processing of the two ATM adapters. Does this already count as high latency? harti