lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080117121408.GS3940@zip.com.au>
Date:	Thu, 17 Jan 2008 23:14:08 +1100
From:	CaT <cat@....com.au>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.24-rc7: memory leak?

On Thu, Jan 17, 2008 at 01:07:12PM +0100, Peter Zijlstra wrote:
> On Thu, 2008-01-17 at 22:40 +1100, CaT wrote:
> > > How much memory does:
> > > 
> > >   echo 3 > /proc/sys/vm/drop_caches
> > > 
> > > gain you?
> > 
> > 56M used now. 
> 
> Good :-)

Indeed. :)

> > Should all this cache usage not be counted towards the
> > 'Cached' entry in meminfo rather then getting counted as part of used
> > ram. 
> 
> Cached is only the page-cache, not all the other caches we have..
> This someones confuses people, but one gets used to it. slabinfo allows
> one to easily view others.

So what would I have to do to find out the real amount of memory free?
Would that be the MemFree field in /proc/meminfo plus, from
/proc/slabinfo, *_cache and size-*?

If that's the case it would seem to be somewhat of a pain to get and
kind of out of left field as I'd say most people would expect MemFree to
indicate the amount of memory that's no longer freely available
(ignoring swapping it out for simplicities sake).

I'm wondering as I'm trying to monitor this stuff and I've just found
out that the easily accessible values are not as useful as I previously
thought.

-- 
    "To the extent that we overreact, we proffer the terrorists the
    greatest tribute."
    	- High Court Judge Michael Kirby
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ