From: Linus Torvalds <torvalds@transmeta.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Lawrence Manning <lawrence@aslak.demon.co.uk>,
Linux Kernel <linux-kernel@vger.rutgers.edu>,
linux-mm@kvack.org
Subject: Re: Basic testing shows 2.3.99-pre9-3 bad, pre9-2 good
Date: Sun, 21 May 2000 12:17:25 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10005211215060.1429-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0005211609170.9939-100000@duckman.distro.conectiva>
On Sun, 21 May 2000, Rik van Riel wrote:
> On Sun, 21 May 2000, Lawrence Manning wrote:
>
> > That's my observation anyway. I did some dd and bonnie tests
> > and got abismal results :-( Machine unusable during dd write
> > etc. pre9-2 on the other hand is close to being as smooth as,
> > say, 2.3.51. What happened? ;)
What happened was really that I did a partial integration just to make it
easier to synchronize. I wanted to basically have pre9-2 + quintela's
patch, but I had too many emails to go through and too many changes of my
own in this area, so I made pre9-3 available so that others could help me
synchronize.
So on't despair, pre9-3 is definitely just a temporary mix of patches, and
is lacking the balancing that Quintela did.
Linus
--
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-21 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10005211837310.627-100000@aslak.demon.co.uk>
2000-05-21 19:11 ` Rik van Riel
2000-05-21 19:17 ` Linus Torvalds [this message]
2000-05-21 19:32 ` Quintela Carreira Juan J.
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.10.10005211215060.1429-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=lawrence@aslak.demon.co.uk \
--cc=linux-kernel@vger.rutgers.edu \
--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