From: Peter Zijlstra <peterz@infradead.org>
To: Andreas Grimm <agrimm61@gmail.com>
Cc: Johannes Weiner <hannes@saeurebad.de>, linux-kernel@vger.kernel.org
Subject: Re: VM - a plenty of inactive memory
Date: Fri, 11 Apr 2008 19:55:15 +0200 [thread overview]
Message-ID: <1207936515.7524.13.camel@twins> (raw)
In-Reply-To: <cf40c6a90804090657j7e76a84foeaf3c1c02d2a7b73@mail.gmail.com>
On Wed, 2008-04-09 at 15:57 +0200, Andreas Grimm wrote:
> Hi Johannes,
>
> i know this. But why the kernel locks that memory for a so long time
> (2 days now)?
It should not be locked (being on the inactive list does not imply that
in any way). Being on the inactive list just means its first in line to
be looked at when memory needs to be reclaimed.
> Is there a way to enforce the reclaiming?
Why would you want to do that for? Would you not rather have a copy of
some page in memory than having to go back to disk to fetch it? Free
memory is a waste, better have something in it that might potentially be
used again.
> And how can i
> find out, which process owns that memory. The problem is, that i can't
> accept, that the free memory fell down to 50MB, when i have 24GB in
> the nirvana.
See above, free memory is a waste. Really, you don't want 24GB of free
memory.
> The system was recently very close to the awkward
> situation to swap to disk, and i bet it will do so in the next few
> days, because it happened before. Unintelligible, if one got that much
> ram.
If it really would have hit swap then it just means you have a _lot_ of
anonymous memory and little page cache pages on that inactive list.
Check Cached and AnonPages.
next prev parent reply other threads:[~2008-04-11 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 9:13 VM - a plenty of inactive memory Andreas Grimm
2008-04-09 13:10 ` Johannes Weiner
2008-04-09 13:57 ` Andreas Grimm
2008-04-09 14:15 ` Dan Noe
2008-04-09 15:01 ` KOSAKI Motohiro
2008-04-09 16:28 ` Andreas Grimm
2008-04-09 18:08 ` Andreas Grimm
2008-04-09 19:56 ` Johannes Weiner
2008-04-09 20:05 ` Andreas Grimm
2008-04-11 17:55 ` Peter Zijlstra [this message]
2008-04-11 13:13 ` Andreas Grimm
2008-04-11 14:34 ` linux-os (Dick Johnson)
[not found] <fa.+S2mzTenrJ0RtdxGRDJkwIoNteA@ifi.uio.no>
[not found] ` <fa.TNkasVGEvLf8IqduH2+YXFyYR1w@ifi.uio.no>
[not found] ` <fa.R/QDJx+PTjNDKcqKW25clMhQ6tg@ifi.uio.no>
2008-04-09 14:32 ` Robert Hancock
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=1207936515.7524.13.camel@twins \
--to=peterz@infradead.org \
--cc=agrimm61@gmail.com \
--cc=hannes@saeurebad.de \
--cc=linux-kernel@vger.kernel.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