From owner-freebsd-hackers  Wed Feb 26 15: 7:38 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4D7AF37B401
	for <freebsd-hackers@freebsd.org>; Wed, 26 Feb 2003 15:07:37 -0800 (PST)
Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 91D2F43F3F
	for <freebsd-hackers@freebsd.org>; Wed, 26 Feb 2003 15:07:36 -0800 (PST)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4])
          by sccrmhc03.attbi.com (sccrmhc03) with ESMTP
          id <20030226230734003007g8rqe>; Wed, 26 Feb 2003 23:07:35 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA99407;
	Wed, 26 Feb 2003 15:07:34 -0800 (PST)
Date: Wed, 26 Feb 2003 15:07:32 -0800 (PST)
From: Julian Elischer <julian@elischer.org>
To: Daxbert <daxbert_news@dweebsoft.com>
Cc: Ed Alley <alley1@llnl.gov>, wea@llnl.gov,
	freebsd-hackers@freebsd.org
Subject: Re: HOWTO track resource leaks in kernel modules?
In-Reply-To: <1046300073.3e5d45a9a9669@ra.dweebsoft.com>
Message-ID: <Pine.BSF.4.21.0302261458040.88133-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG



On Wed, 26 Feb 2003, Daxbert wrote:

> Quoting Julian Elischer <julian@elischer.org>:
> 
> > On Wed, 26 Feb 2003, Ed Alley wrote:
> > > 
> > > Re: Resource leaks
> > > 	<HOWTO track resource leaks in kernel modules?>
> > 
> > what KIND of resource leaks?
> > 
> 
> I guess I asked this question of the wrong list.  I'm interested in
> finding dma allocs, memory allocs, and IRQ/IO allocs which occur
> during a LKM's attached life.  I'm adding the ability to detach
> if_de and was hoping to find assistance on where to look for
> resource tracking tools.

For malloc (in the kernel) you can specify a separate pool for a module,
so that it will account for mallocs for that module separatly.
you can then look at them with vmstat -m


check out sys/malloc.h
and look at MALLOC_DECLARE

is this for 4.x or 5.x?


> 
> --daxbert
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message