From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 4 04:58:53 2012 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 6A058106566C for ; Mon, 4 Jun 2012 04:58:53 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id CBA418FC1E for ; Mon, 4 Jun 2012 04:58:52 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q544wna3003731; Mon, 4 Jun 2012 06:58:49 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id q544wnjO003728; Mon, 4 Jun 2012 06:58:49 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Mon, 4 Jun 2012 06:58:49 +0200 (CEST) From: Wojciech Puchar To: Peter Jeremy In-Reply-To: <20120603205756.GH2675@aspire.rulingia.com> Message-ID: References: <20120603205756.GH2675@aspire.rulingia.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Mon, 04 Jun 2012 06:58:50 +0200 (CEST) Cc: freebsd-hackers@freebsd.org Subject: Re: detailed map of WIRED memory under FreeBSD 9 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: Mon, 04 Jun 2012 04:58:53 -0000 thank you On Mon, 4 Jun 2012, Peter Jeremy wrote: > On 2012-Jun-01 10:19:37 +0200, Wojciech Puchar wrote: >> what tool and how can be used to display detailed map what exactly wired >> memory on my system as it is far way too much (1.5GB out of 4GB RAM). > > The procfs "map" pseudo-file should give you this information on a > per-process level. Unfortunately, the only documentation appears to > be the source (sys/fs/procfs/procfs_map.c) > > -- > Peter Jeremy >