From: "Stephen C. Tweedie" <sct@redhat.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Jan Niehusmann <jan@gondor.com>,
Craig Kulesa <ckulesa@loke.as.arizona.edu>,
linux-mm@kvack.org
Subject: Re: PATCH: Possible solution to VM problems (take 2)
Date: Thu, 18 May 2000 14:49:18 +0100 [thread overview]
Message-ID: <20000518144918.C5672@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0005181038230.14198-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Thu, May 18, 2000 at 10:41:05AM -0300
Hi,
On Thu, May 18, 2000 at 10:41:05AM -0300, Rik van Riel wrote:
>
> I think I have this mostly figured out. I'll work on
> making some small improvements over Quintela's patch
> that will make the system behave decently in this
> situation too.
Good, because apart from the write performance, Juan's patch seems to
work really well for the stress tests I've thrown at it so far.
--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-05-18 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-14 9:48 Summary of recent VM behavior [2.3.99-pre8] Craig Kulesa
2000-05-18 10:17 ` PATCH: Possible solution to VM problems (take 2) Craig Kulesa
2000-05-18 10:59 ` Jan Niehusmann
2000-05-18 13:41 ` Rik van Riel
2000-05-18 13:49 ` Stephen C. Tweedie [this message]
2000-05-16 19:32 [dirtypatch] quickhack to make pre8/9 behave (fwd) Rik van Riel
2000-05-17 0:28 ` PATCH: less dirty (Re: [dirtypatch] quickhack to make pre8/9 behave (fwd)) Juan J. Quintela
2000-05-17 20:45 ` PATCH: Possible solution to VM problems Juan J. Quintela
2000-05-17 23:31 ` PATCH: Possible solution to VM problems (take 2) Juan J. Quintela
2000-05-18 0:12 ` Juan J. Quintela
2000-05-18 1:07 ` Rik van Riel
2000-05-21 8:14 ` Linus Torvalds
2000-05-21 16:01 ` Rik van Riel
2000-05-21 17:15 ` Linus Torvalds
2000-05-21 19:02 ` Rik van Riel
2000-05-18 5:58 Neil Schemenauer
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=20000518144918.C5672@redhat.com \
--to=sct@redhat.com \
--cc=ckulesa@loke.as.arizona.edu \
--cc=jan@gondor.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
/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