Message-ID: <416823E6.6020008@free.fr>
Date: Sat, 09 Oct 2004 19:46:14 +0200
From: Eric Valette <eric.valette@free.fr>
Reply-To: eric.valette@free.fr
Organization: HOME
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5
MIME-Version: 1.0
To: Albert Cahalan <albert@users.sf.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Inconsistancies in /proc (status vs statm) leading	to	wrong	documentation
 (proc.txt)
References: <1097329771.2674.4036.camel@cube>  <4167F0D7.3020502@free.fr>	 <1097339477.2669.4212.camel@cube>  <416815FD.2060502@free.fr> <1097341175.2669.4257.camel@cube>
In-Reply-To: <1097341175.2669.4257.camel@cube>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 870
Lines: 31

Albert Cahalan wrote:

> Not quite, but close. Those that know are willing
> to read the kernel code, including that of past
> releases, can certainly use the statm file.

Sure but it while doing that after readding the official documentation 
that the trouble began...


> For that, go directly to /proc/*/maps and be happy.

That's a good point. Very usefull for knowing which dynamic library 
account for what size. I start wondering if dynamic libraries and 
mlockall works well toghether..

> You may also want the RSS from /proc/*/status.

Well RSS = VmSize after mlockall I guess

Thanks for the maps hint,

-- eric


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/