From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Ying Chen/Almaden/IBM <ying@almaden.ibm.com>,
linux-mm@kvack.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] fix for VM test9-pre,
Date: Mon, 2 Oct 2000 21:52:17 +0200 [thread overview]
Message-ID: <20001002215217.C21473@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.21.0010021626460.22539-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Mon, Oct 02, 2000 at 04:28:48PM -0300
On Mon, Oct 02, 2000 at 04:28:48PM -0300, Rik van Riel wrote:
> Yup, indeed. I guess we need some extra logic to prevent the
> system from trying to fill all of low memory with dirty
> pages just because all of the highmem pages are free.
A dirty page is allocated in the HIGHMEM immediatly because it's allocated with
GFP_HIGHMEM (see page_cache_alloc() macro). Only the I/O is slower then
(compared to a non highmem machine) because we need bounce buffers for it (and
that trashes mem bus and it makes the I/O slower but it's not a matter of
virtual memory balancing as far I can see).
> Unfortunately, I DID get a few bug reports about
> 2.4.0-test6 and earlier kernels that DID show this
> bug ...
So that may be yet another MM bug, since I remeber Ying said he didn't seen the
bad behaviour in test6.
> I can dig out the bug report if you want ;)
I read one that you sent to TYTSO and I believe classzone should take care of
that highmem problem.
Andrea
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-10-02 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-02 16:40 Ying Chen/Almaden/IBM
2000-10-02 17:07 ` Rik van Riel
2000-10-02 19:25 ` Andrea Arcangeli
2000-10-02 19:28 ` Rik van Riel
2000-10-02 19:52 ` Andrea Arcangeli [this message]
2000-10-02 19:56 ` Rik van Riel
2000-10-02 19:01 Ying Chen/Almaden/IBM
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=20001002215217.C21473@athlon.random \
--to=andrea@suse.de \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=riel@conectiva.com.br \
--cc=ying@almaden.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox