From: "Stephen C. Tweedie" <sct@redhat.com>
To: riel@nl.linux.org
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-mm@kvack.org
Subject: Re: pressuring dirty pages (2.3.99-pre6)
Date: Tue, 25 Apr 2000 10:35:52 +0100 [thread overview]
Message-ID: <20000425103552.A4627@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0004241922270.5572-100000@duckman.conectiva>; from riel@conectiva.com.br on Mon, Apr 24, 2000 at 07:42:12PM -0300
Hi,
On Mon, Apr 24, 2000 at 07:42:12PM -0300, Rik van Riel wrote:
>
> That will not work. The problem isn't that kswapd eats cpu,
> but the problem is that the dirty pages completely dominate
> physical memory.
That isn't a "problem". That's a state. Of _course_ memory usage
is going to be dominated by whichever sort of page is being
predominantly used.
So we need to identify the real problem. Is 2.3 much worse than
2.2 at this dirty-write-mmap test? Are we seeing swap fragmentation
reducing swap throughput? Is the VM simply keeping insufficient
memory available for tasks other than the highly paging one?
--Stephen
--
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-04-25 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-24 19:54 Rik van Riel
2000-04-24 21:27 ` Stephen C. Tweedie
2000-04-24 22:42 ` Rik van Riel
2000-04-25 9:35 ` Stephen C. Tweedie [this message]
2000-04-25 15:25 ` Rik van Riel
2000-04-25 13:58 ` Eric W. Biederman
2000-04-25 14:27 Mark_H_Johnson.RTS
2000-04-25 16:30 ` Stephen C. Tweedie
2000-04-25 19:14 ` Eric W. Biederman
2000-04-25 19:47 ` Rik van Riel
2000-04-26 11:43 ` Stephen C. Tweedie
2000-04-26 11:06 ` Stephen C. Tweedie
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=20000425103552.A4627@redhat.com \
--to=sct@redhat.com \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.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