From: Rik van Riel <riel@conectiva.com.br>
To: Lawrence Manning <lawrence@aslak.demon.co.uk>
Cc: Linux Kernel <linux-kernel@vger.rutgers.edu>,
linux-mm@kvack.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Basic testing shows 2.3.99-pre9-3 bad, pre9-2 good
Date: Sun, 21 May 2000 16:11:21 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0005211609170.9939-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.10.10005211837310.627-100000@aslak.demon.co.uk>
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? ;)
OK, I guess this means shrink_mmap() should not wait on
*every* locked buffer it runs into ;)
This will destroy both latency (we end up waiting for a
*lot* of buffers) and throughput (waiting on buffers could
interfere with request sorting if we're unlucky).
> I also should chip in to say that 2.2.15 is abit sick IO wise
> for me too.
I'm working on it :)
regards,
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
Wanna talk about the kernel? irc.openprojects.net / #kernelnewbies
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 parent reply other threads:[~2000-05-21 19:11 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 [this message]
2000-05-21 19:17 ` Linus Torvalds
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.21.0005211609170.9939-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=lawrence@aslak.demon.co.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--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