From owner-freebsd-net@FreeBSD.ORG Wed Nov 30 15:24:06 2005 Return-Path: X-Original-To: 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 C20F716A41F for ; Wed, 30 Nov 2005 15:24:06 +0000 (GMT) (envelope-from nielsen-list@memberwebs.com) Received: from mail.npubs.com (mail.wsfamily.com [209.66.100.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB2DF43D46 for ; Wed, 30 Nov 2005 15:24:04 +0000 (GMT) (envelope-from nielsen-list@memberwebs.com) From: Nate Nielsen User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler References: <438CE0A8.4010205@memberwebs.com> <438D0896.1070808@memberwebs.com> <438D1A99.6000803@errno.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20051130153839.53AA570DCE3@mail.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Wed, 30 Nov 2005 15:38:39 +0000 (GMT) Cc: freebsd-net@freebsd.org Subject: Re: Memory leak in net80211 on FBSD 6.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nielsen@memberwebs.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2005 15:24:06 -0000 Sam Leffler wrote: > Nate Nielsen wrote: >> I've put debugging code in node_alloc() and node_free() (in >> net80211/ieee80211_node.c) and can confirm that thousands of >> ieee80211_node structures are being allocated, at a cost of 1K a piece. >> >> I'll continue to look into this (stumbling about), but if anyone has any >> advice or ideas of where to look, I'd be eternally grateful. > > Please don't spam lots of groups. Apologies. > I'm aware of the leak (David Young > found it in netbsd) and have a partial fix. I'll send it to you directly. Wonderful. Looking forward to that. I've had other problems with rate control in the atheros driver. But I'll wait till I apply your patch before I look into them further, as I'd imagine it's possible the problems are related. Cheers, Nate