From: "Dr. Werner Fink" <werner@suse.de>
To: Zlatko.Calusic@CARNet.hr
Cc: linux-mm@kvack.org
Subject: Re: Ideas for memory management hackers.
Date: Wed, 10 Dec 1997 16:21:40 +0100 [thread overview]
Message-ID: <199712101521.QAA25114@boole.fs100.suse.de> (raw)
In-Reply-To: <87g1o1nxxd.fsf@atlas.infra.CARNet.hr> (message from Zlatko Calusic on 10 Dec 1997 14:13:34 +0100)
[patch deleted ... found at http://www.fys.ruu.nl/~riel/ :-)]
>
> It was originally developed for 2.1.61, but it works perfectly on
> 2.1.71 (I just checked). It was posted on linux-kernel list during
> recent problems (massive unsubscribe), so many people missed it.
>
> Now some comments on the patch:
>
> I had nasty lockups with all 2.1 kernels. I traced problem down to the
> network stuff which was trying to allocate pages of order 2 what was
> constantly failing. Problem was (and still is!) that Linux doesn't
> swap pages out to get more free memory if it already has
> free_pages_high or more free pages. Of course, it is correct
> behaviour, but... sometimes memory is completely fragmented, and all
> free chunks are of one or two pages, so there's no way you could get
> 16KB of contiguous memory (even if you have 512KB free!). Networking
> can't proceed without that and if you're logged remotely you're in
> fact completely disconnected.
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.
Werner
next prev parent reply other threads:[~1997-12-10 15:27 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 [this message]
1997-12-10 19:13 ` Benjamin C.R. LaHaise
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=199712101521.QAA25114@boole.fs100.suse.de \
--to=werner@suse.de \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=linux-mm@kvack.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