All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
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: Wed, 09 Apr 2008 08:32:27 -0600	[thread overview]
Message-ID: <47FCD37B.3040103@shaw.ca> (raw)
In-Reply-To: <fa.R/QDJx+PTjNDKcqKW25clMhQ6tg@ifi.uio.no>

Andreas Grimm wrote:
> Hi Johannes,
> 
> i know this. But why the kernel locks that memory for a so long time
> (2 days now)? Is there a way to enforce the reclaiming? 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. 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.
> 
> Bye, Andreas

The memory should not be locked. If the kernel has no reason to reclaim 
the memory, it won't, though.

       reply	other threads:[~2008-04-09 14:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2008-04-11 13:13   ` Andreas Grimm
2008-04-11 14:34     ` linux-os (Dick Johnson)

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=47FCD37B.3040103@shaw.ca \
    --to=hancockr@shaw.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.