From: Rik van Riel <riel@conectiva.com.br>
To: Mike Galbraith <mikeg@weiden.de>
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-pre1 vmfix (rev 8)
Date: Fri, 21 Jul 2000 17:19:31 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0007211716580.22938-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.Linu.4.10.10007180806290.591-100000@mikeg.weiden.de>
On Tue, 18 Jul 2000, Mike Galbraith wrote:
> On Tue, 18 Jul 2000, Roger Larsson wrote:
>
> > * I get 10% better throughput than 2.4.0-test4, YMMV
>
> Seeing about the same improvement here.. lightly tested.
Part of the code looks bogus though.
Linus, would it be possible to have a rule in place
that nobody submits VM code unless they accompany it
with an explanation of _why_ their code is supposed
to work?
There seem to be too many "random tweaks" in the current
VM code where nobody has an explanation of why the code works and
what exactly it is supposed to do...
regards,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
--
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-21 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-18 1:14 Roger Larsson
2000-07-18 6:11 ` Mike Galbraith
2000-07-21 20:19 ` Rik van Riel [this message]
2000-07-18 7:21 ` Roger Larsson
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.4.21.0007211716580.22938-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mikeg@weiden.de \
--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