From owner-freebsd-hackers@FreeBSD.ORG  Tue Feb  8 15:04:50 2011
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 42B4E106564A
	for <freebsd-hackers@freebsd.org>; Tue,  8 Feb 2011 15:04:50 +0000 (UTC)
	(envelope-from alan.l.cox@gmail.com)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com
	[209.85.161.54])
	by mx1.freebsd.org (Postfix) with ESMTP id A50B18FC19
	for <freebsd-hackers@freebsd.org>; Tue,  8 Feb 2011 15:04:49 +0000 (UTC)
Received: by fxm16 with SMTP id 16so6469018fxm.13
	for <multiple recipients>; Tue, 08 Feb 2011 07:04:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:reply-to:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type;
	bh=rBArosaNQAd5g4+NZ0kAu/CDKzDSUuUc83Z3tq5R+7w=;
	b=gN8hiv4mTFWl4peYN75rEj+oWf/SS5o61KhiTVVlokkuo1UjBUM2mclhrfhyC1s+Go
	X8/g0NHmRaPHFev7gJHf60Xt8Jd4x4g6dn5bZ6uloCn6JnyVm4S08Mi4Z/G8eZz+qSO6
	2Wlygk5wCCGewuFPiPomlbTIMkrOz2vSQoXfg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:reply-to:in-reply-to:references:date:message-id
	:subject:from:to:cc:content-type;
	b=aaTbDH802azyB4qERZi+YPEI9M9o+1qsU8b2VRi5fI4134WRoXsLNgTGFXPHfz4R0v
	QgjqVXyIHhbxWNmJy7dZnfyd9pdYygnmFtIc02sia8+AKFkyqW1tjj50o83qYv4mNe+c
	bTe56ayiXmWake1x5baL+wUkVLWTEy1DT+v0A=
MIME-Version: 1.0
Received: by 10.223.72.206 with SMTP id n14mr7587887faj.2.1297177488537; Tue,
	08 Feb 2011 07:04:48 -0800 (PST)
Received: by 10.223.120.205 with HTTP; Tue, 8 Feb 2011 07:04:48 -0800 (PST)
In-Reply-To: <iirce4$urj$1@dough.gmane.org>
References: <iirce4$urj$1@dough.gmane.org>
Date: Tue, 8 Feb 2011 09:04:48 -0600
Message-ID: <AANLkTikNw4G7MDHwCAmxfzFGUBxQb1S9pUjTM_-g3K+y@mail.gmail.com>
From: Alan Cox <alan.l.cox@gmail.com>
To: Ivan Voras <ivoras@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: freebsd-hackers@freebsd.org
Subject: Re: Analyzing wired memory?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alc@freebsd.org
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 15:04:50 -0000

On Tue, Feb 8, 2011 at 6:20 AM, Ivan Voras <ivoras@freebsd.org> 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?

Alan