mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wappler Marcel <Marcel.Wappler@bridgeco.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: VM: page reclaim does not work on ARM9? [resend]
Date: Thu, 28 Aug 2008 10:01:19 +0200	[thread overview]
Message-ID: <462ADBE7F1A69C438B7E2ED56007E6F5ABF9A43F2B@exch10.BC-Int.NET> (raw)

I do need some help to understand what's going on in the VM
of the Linux kernel...

I wrote a little script which generates a C app with
millions of lines of dumb linear running code and a endless
loop at the end. I run this app on both PC Linux (swapping
enabled) and embedded Linux (Kernel 2.6.24.7, ARM9, swapping
disabled).

The app shall consume a lot of code pages which are used
only once (to run the linear code in it) and then stay in
the endless loop and never touch all the other pages in
memory. Then I consume all of the remaining memory of the
system through generating a big file on the tmpfs (whose
data resides in memory) with the help of /dev/zero and "dd".

My expectation was: the VM shall steal (reclaim) all the
only once touched pages containing those dumb linear code of
the app.

My observation is: "top" shows that the app is consuming
constantly the same huge amount of residential memory during
the decreasing free memory space. At some moment the kernel
starts a OOM killer on the app instead of reclaiming its
unused code pages.

Keep in mind: the behaviour is the same on both PC Linux (2
GB RAM) and ARM Linux (32MB RAM ) with and without swapping
enabled.

So for me it looks like that any page which is containing
code never gets reclaimed from the application it belongs to
regardless of its usage.

Any idias, whats going on?

best regards, Marcel

PS: Please CC me on reply...

             reply	other threads:[~2008-08-28  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Ach0m4cSiApNdLdFScC3DSTHVH8H7w==>
2008-08-28  8:01 ` Wappler Marcel [this message]
2008-08-30  0:49   ` KOSAKI Motohiro

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=462ADBE7F1A69C438B7E2ED56007E6F5ABF9A43F2B@exch10.BC-Int.NET \
    --to=marcel.wappler@bridgeco.net \
    --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®