From: Rik van Riel <riel@conectiva.com.br>
To: Tom Leete <tleete@mountain.net>
Cc: linux-mm@kvack.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] fix for VM test9-pre7
Date: Mon, 2 Oct 2000 12:51:42 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0010021250180.22539-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <39D87F3A.7D21E18@mountain.net>
On Mon, 2 Oct 2000, Tom Leete wrote:
> I ran lmbench on test9-pre7 with and without the patch.
>
> Test machine was a slow medium memory UP box:
> Cx586@120Mhz, no optimizations, 56M
>
> I still experience instability on this machine with both the
> patched and vanilla kernel. It usually takes the form of
> sudden total lockups, but on occasion I have seen oops +
> panic at boot.
If you could decode the oops or mail us the panic, we
might find out if this is a VM related problem or not...
> This summary doesn't show any performance advantage to the
> patch, but the detailed plots show that memory access
> latency degrades more gracefully wrt array size.
That's because this benchmark has a very artificial page
access pattern, that doesn't really benefit from any kind
of page replacement. ;)
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-10-02 15:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-02 3:42 Rik van Riel
2000-10-02 8:18 ` Roger Larsson
2000-10-02 10:00 ` Ignore my: " Roger Larsson
2000-10-02 15:48 ` Rik van Riel
2000-10-02 15:45 ` Rik van Riel
2000-10-02 12:05 ` ehrhardt
2000-10-02 15:49 ` Rik van Riel
2000-10-02 12:27 ` Tom Leete
2000-10-02 15:51 ` Rik van Riel [this message]
2000-10-02 21:20 ` Tom Leete
2000-10-02 16:46 ` Christoph Rohland
2000-10-02 17:17 ` Rik van Riel
2000-10-04 7:45 ` Christoph Rohland
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.0010021250180.22539-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=linux-mm@kvack.org \
--cc=tleete@mountain.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