From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: "Dr. Werner Fink" <werner@suse.de>
Cc: linux-mm@kvack.org
Subject: Re: Ideas for memory management hackers.
Date: Tue, 9 Dec 1997 18:10:37 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.971209180740.4287C-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199712091611.RAA05335@boole.fs100.suse.de>
On Tue, 9 Dec 1997, Dr. Werner Fink wrote:
> >
> > I have integrated mmap aging in kswapd, without the need for
> > vhand, in 2.1.71 (experimental). As ppp isn't working in 2.1.71
> > I'm back to 2.1.66 now, but I have seen kswapd use over 10% of
> > CPU for short times now :(
>
> Q: if ageing is now a separate part the CPU usage of freeing a page
> in kswapd and __get_free_pages should drop, shouldn't it?
In this new patch, aging is not a separate process, because
vhand has a design flaw in it :(( (I think).
The page->referenced flag is not updated by the mmu, instead
it updates the pte->accessed flag... Now vhand can't handle
normal user pages (this explains the higher swap usage) and
they are swapped more often, actually, they are swapped by a
second chance fifo algorithm now, so nobody noticed decreased
performance...
>
> > I think I'll send it to Linus (together with Zlatko's
> > big-order hack) as a bug-fix (we're on feature-freeze after all:)
> > for inclusion in 2.1.72...
> >
> > opinions please,
>
> Q2: Is the patch available (ftp/http) for testing/reading?
RSN...
Rik.
--
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...
next prev parent reply other threads:[~1997-12-09 17:31 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 [this message]
1997-12-10 13:13 ` Zlatko Calusic
1997-12-10 15:21 ` Dr. Werner Fink
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=Pine.LNX.3.91.971209180740.4287C-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--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