From: Mike Galbraith <mikeg@weiden.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Roger Larsson <roger.larsson@norran.net>,
Linus Torvalds <torvalds@transmeta.com>,
"linux-kernel@vger.rutgers.edu" <linux-kernel@vger.rutgers.edu>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] test5-1 vm fix
Date: Mon, 17 Jul 2000 21:01:18 +0200 (CEST) [thread overview]
Message-ID: <Pine.Linu.4.10.10007171948160.347-100000@mikeg.weiden.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0007171143100.30603-100000@duckman.distro.conectiva>
On Mon, 17 Jul 2000, Rik van Riel wrote:
> On Mon, 17 Jul 2000, Mike Galbraith wrote:
> > On Sun, 16 Jul 2000, Rik van Riel wrote:
> > > On Sun, 16 Jul 2000, Mike Galbraith wrote:
> > > > Unfortunately, this didn't improve anything here.
> > >
> > > As was to be expected ...
> >
> > one can only hope and test.
>
> Alternatively, one can learn from the patches and
> mistakes of others and try to understand how stuff
> works.
I read them all from top to bottom, and listen at full volume.
> > Do you already know what it's up to during one of these nasty
> > stalls?
>
> There's nothing wrong with the current VM that wasn't
> fixed in one of my patches the last 8 weeks.
>
> (except for the fundamental design flaws, which I will
> fix in the *next* N+1 weeks)
I look forward to trying out the result.
> regards,
>
> Rik
Cheers,
-Mike
--
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-07-17 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-15 23:07 Roger Larsson
2000-07-16 8:16 ` Mike Galbraith
2000-07-16 19:33 ` Rik van Riel
2000-07-17 7:10 ` Roger Larsson
2000-07-17 7:46 ` Mike Galbraith
2000-07-17 14:44 ` Rik van Riel
2000-07-17 19:01 ` Mike Galbraith [this message]
2000-07-17 17:21 ` Mark Hahn
2000-07-17 20:22 ` Mike Galbraith
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.Linu.4.10.10007171948160.347-100000@mikeg.weiden.de \
--to=mikeg@weiden.de \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=roger.larsson@norran.net \
--cc=torvalds@transmeta.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