From: CaT <cat@zip.com.au>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc7: memory leak?
Date: Thu, 17 Jan 2008 23:28:57 +1100 [thread overview]
Message-ID: <20080117122856.GT3940@zip.com.au> (raw)
In-Reply-To: <1200572511.28661.20.camel@twins>
On Thu, Jan 17, 2008 at 01:21:51PM +0100, Peter Zijlstra wrote:
> > 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 somewhat confused as to what you're saying. How would anyone expect
> MemFree to be memory that is _not_ freely available?
I think we have conflicting ideas of what 'freely available' means here
which is causing the confusion. :)
> Or are you asking how to compute the amount of freeable memory, that is
> memory that isn't currently free, but could be freed up under pressure?
Yes. I think I am. (heh)
> If that is indeed your question, then yes, thats rather hard as slabinfo
> and the like don't indicate which buckets have shrinkers (but even if
Ah. Foo.
> they would have shrinkers there is no guarantee they'd be able to shrink
> 100%)
Whacky.
:/
--
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael Kirby
next prev parent reply other threads:[~2008-01-17 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 6:34 2.6.24-rc7: memory leak? CaT
2008-01-17 11:21 ` Pekka Enberg
2008-01-17 11:22 ` Peter Zijlstra
2008-01-17 11:40 ` CaT
2008-01-17 12:07 ` Peter Zijlstra
2008-01-17 12:14 ` CaT
2008-01-17 12:21 ` Peter Zijlstra
2008-01-17 12:28 ` CaT [this message]
2008-01-17 12:22 ` KOSAKI Motohiro
2008-01-17 12:35 ` CaT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080117122856.GT3940@zip.com.au \
--to=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox