From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: "Dr. Werner Fink" <werner@suse.de>
Cc: Zlatko.Calusic@CARNet.hr, linux-mm@kvack.org
Subject: Re: Ideas for memory management hackers.
Date: Wed, 10 Dec 1997 14:13:14 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.95.971210133924.5452C-100000@as200.spellcast.com> (raw)
In-Reply-To: <199712101521.QAA25114@boole.fs100.suse.de>
On Wed, 10 Dec 1997, Dr. Werner Fink wrote:
> In other words a better memory defragmentation is needed for 2.2, isn't it?
> A simple approach could be an addition address check during the scans
> in shrink_mmap (mm/filemap.c) instead of a freeing the first unused
> (random) page. This could be used in the first few priorities to free pages
> mostly useful for defragmentation.
>
> An other approach is Ben's anonymous ageing of physical task pages
> found in http://www.kvack.org/~blah/patches/v2_1_47_ben1.gz ...
> this approach gives a link of the pte of a page needed for ageing
> the page.
The past few times this has come up, the general argument from a few core
people is that if one *really* cares to find the pte's pointing to a page,
traversing the list of vma's attached to the inode, for which a pointer
already exists, would be sufficient. Until I come up with something
really kick-ass, I really doubt the pte-list stuff will be included.
-ben
next prev parent reply other threads:[~1997-12-10 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <348D3B36.673BEE82@nospam.isltd.insignia.co.uk>
1997-12-09 14:53 ` Rik van Riel
1997-12-09 16:11 ` Dr. Werner Fink
1997-12-09 17:10 ` Rik van Riel
1997-12-10 13:13 ` Zlatko Calusic
1997-12-10 15:21 ` Dr. Werner Fink
1997-12-10 19:13 ` Benjamin C.R. LaHaise [this message]
1997-12-10 21:55 ` Rik van Riel
1997-12-09 17:45 ` Benjamin C.R. LaHaise
1997-12-09 17:53 ` Rik van Riel
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=Pine.LNX.3.95.971210133924.5452C-100000@as200.spellcast.com \
--to=blah@kvack.org \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=linux-mm@kvack.org \
--cc=werner@suse.de \
/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