From: John Richard Moser <nigelenki@comcast.net>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory compression (again). . help?
Date: Tue, 28 Feb 2006 07:06:54 -0500 [thread overview]
Message-ID: <44043CDE.6040204@comcast.net> (raw)
In-Reply-To: <aec7e5c30602272120l54a3e8c9k2db51a1c86823f7b@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Magnus Damm wrote:
> On 2/28/06, John Richard Moser <nigelenki@comcast.net> wrote:
>> Hmm, I can't see where the kernel checks to see which pages are least
>> used. . . . anyone good with the VM can point me in the right direction?
>
> The page reclaim code responsible for shrinking the LRUs code be found
> in mm/vmscan.c. That file contains a lot of code, my recommendation to
> you is to have a look at shrink_zone() which is responsible for
> rotating and shrinking the active and inactive lists.
>
Thanks, I'll take a look.
> Also, If you want to compress pages that normally would be swapped
> out, then I recommend you to have a look at the functions in
> mm/swap_state.c and see how swap space gets allocated and freed.
>
Mm. Ok.
> If you need to know more about the Linux VM then I recommend you to
> buy the excellent book "Understanding the Linux Virtual Memory
> Manager" written by Mel Gorman, ISBN 0-13-145348-3. My copy of that
> book covers Linux-2.4 and has some comments about 2.6 too.
>
I'll shoot from the hip, my foot grows back.
> / magnus
>
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
We will enslave their women, eat their children and rape their
cattle!
-- Evil alien overlord from Blasto
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEBDzdhDd4aOud5P8RApCXAKCASRwqJqXD/8rHh84x3tzkntC6jQCeMeqS
9B7IgG3aCEJOOXrOsxSMp3o=
=ZLh3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-02-28 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 1:03 Memory compression (again). . help? John Richard Moser
2006-02-28 3:27 ` John Richard Moser
2006-02-28 5:20 ` Magnus Damm
2006-02-28 12:06 ` John Richard Moser [this message]
2006-02-28 16:24 ` Rik van Riel
2006-02-28 17:02 ` John Richard Moser
2006-02-28 4:00 ` Alexander E. Patrakov
2006-02-28 12:18 ` John Richard Moser
2006-02-28 12:38 ` Asbjørn Sannes
2006-02-28 16:06 ` John Richard Moser
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=44043CDE.6040204@comcast.net \
--to=nigelenki@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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.