From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 8 18:27:23 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10201106566B; Tue, 8 Feb 2011 18:27:23 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id DC7A78FC0C; Tue, 8 Feb 2011 18:27:22 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 71DC446B1A; Tue, 8 Feb 2011 13:27:22 -0500 (EST) Date: Tue, 8 Feb 2011 18:27:22 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: alc@freebsd.org In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Ivan Voras Subject: Re: Analyzing wired memory? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2011 18:27:23 -0000 On Tue, 8 Feb 2011, Alan Cox wrote: > On Tue, Feb 8, 2011 at 6:20 AM, Ivan Voras wrote: > >> Is it possible to track by some way what kernel system, process or thread >> has wired memory? (including "data exists but needs code to extract it") >> > No. > > >> I'd like to analyze a system where there is a lot of memory wired but not >> accounted for in the output of vmstat -m and vmstat -z. There are no user >> processes which would lock memory themselves. >> >> Any pointers? >> > Have you accounted for the buffer cache? John and I have occasionally talked about making procstat -v work on the kernel; conceivably it could also export a wired page count for mappings where it makes sense. Ideally procstat would drill in a bit and allow you to see things at least at the granularty of "this page range was allocated to UMA". Robert