From owner-freebsd-net@FreeBSD.ORG Tue May 6 18:08:07 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2E5E10656B8 for ; Tue, 6 May 2008 18:08:07 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outT.internet-mail-service.net (outt.internet-mail-service.net [216.240.47.243]) by mx1.freebsd.org (Postfix) with ESMTP id 8026E8FC21 for ; Tue, 6 May 2008 18:08:07 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Tue, 06 May 2008 19:03:44 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id CE4F82D600D; Tue, 6 May 2008 10:56:20 -0700 (PDT) Message-ID: <48209BC4.5080602@elischer.org> Date: Tue, 06 May 2008 10:56:20 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Oleksandr Samoylyk References: <48207C8B.4020509@samoylyk.sumy.ua> In-Reply-To: <48207C8B.4020509@samoylyk.sumy.ua> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: Problems with netgraph X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2008 18:08:08 -0000 Oleksandr Samoylyk wrote: > Dear developers, > > Please read this thread: > http://lists.freebsd.org/pipermail/freebsd-net/2008-May/017891.html > > I'm using no encryption and no compression in mpd, so netgraph should fly. > It seems to get bad after 500 sessions... > > In FreeBSD 6 - it's swi1: net - 100% CPU > In FreeBSD 7 - it's em0 taskq - 100% CPU unfortunatly I've been totally ignoring this thread because it said "trouble with em" in the topic.. If you'd said trouble with mpd then maybe I'd have looked earlier.. > > After playing with it I can make guess that's a netgraph problem. > > Maybe it's a poor design in netgraph the way it handle its tables and > it's is probably not designed to add so many interfaces. how many? > > Might be there something in the source code I can edit to improve the > table lookups or hash table or whatever netgraph use to store and > process the node information and do the ppp/gre work. netgraph just had some work done on it for this exact reason, but you may be jumping the gun a bit.. >