mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Andreas Grimm" <agrimm61@gmail.com>
To: "Johannes Weiner" <hannes@saeurebad.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VM - a plenty of inactive memory
Date: Wed, 9 Apr 2008 15:57:48 +0200	[thread overview]
Message-ID: <cf40c6a90804090657j7e76a84foeaf3c1c02d2a7b73@mail.gmail.com> (raw)
In-Reply-To: <874pabrx6b.fsf@saeurebad.de>

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


2008/4/9, Johannes Weiner <hannes@saeurebad.de>:
> Hi,
>
>
>  "Andreas Grimm" <agrimm61@gmail.com> writes:
>
>  > Hello everybody,
>  >
>  > i got a weird problem with one of my servers. It's a Intel SR2500AL
>  > with 32GB of RAM.
>  > Looking at the memory usage of the system, something is going totally
>  > wrong. The crucial numbers from /proc/meminfo are:
>  >
>  > MemTotal: 33265916 kB
>  > MemFree: 416168 kB
>  > Inactive: 24630428 kB (24GB? whooaaa)
>  >
>  > Another system with only 16GB, same amount of users and load, shows a
>  > more normal behaviour:
>  >
>  > MemTotal: 16619808 kB
>  > MemFree: 6912676 kB
>  > Inactive: 1774364 kB
>  >
>  > Why does the 32GB-System have this plenty of inactive memory. Is there
>  > a way to find out, what the kernel is holding in readiness (that's the
>  > definition of inactive memory afaik)?
>
>
> Inactive pages are marked in use but haven't been touched for some time.
>  These are candidates for memory reclaiming.
>
>  If nothing memory consuming happens, the kswapd should reclaim them back
>  eventually.
>
>         Hannes
>

  reply	other threads:[~2008-04-09 13:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  9:13 Andreas Grimm
2008-04-09 13:10 ` Johannes Weiner
2008-04-09 13:57   ` Andreas Grimm [this message]
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)
     [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=cf40c6a90804090657j7e76a84foeaf3c1c02d2a7b73@mail.gmail.com \
    --to=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

all inboxes | Powered by JetHome®