From owner-freebsd-hackers Thu Feb 27 6:46:12 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 38C4C37B401 for ; Thu, 27 Feb 2003 06:46:11 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 601A343FBF for ; Thu, 27 Feb 2003 06:46:10 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0140.cvx40-bradley.dialup.earthlink.net ([216.244.42.140] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18oPIS-0000ph-00; Thu, 27 Feb 2003 06:46:04 -0800 Message-ID: <3E5E2459.689F4E9D@mindspring.com> Date: Thu, 27 Feb 2003 06:44:41 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Daxbert Cc: Julian Elischer , Ed Alley , wea@llnl.gov, freebsd-hackers@freebsd.org Subject: Re: HOWTO track resource leaks in kernel modules? References: <1046300073.3e5d45a9a9669@ra.dweebsoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4d372d43fb3e906698640bfb871ba1b95350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Daxbert wrote: > Quoting Julian Elischer : > > On Wed, 26 Feb 2003, Ed Alley wrote: > > > > > > Re: Resource leaks > > > > > > > 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. There are significant changes in the allocator memory architecture, which you would need to address in order to find the necessary statistics. The code you would examine to see what you need to look at these days would be whatever the most recent version of "vmstat -m" does in order to get its information. With that knowledge in hand, please see: http://www.freebsd.org/~terry/testset.txt http://www.freebsd.org/~terry/testset.tar.gz.uu which is a set of test code that allows you to exercise kernel code paths, and which will flag memory allocation leaks for you. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message