From: Stephan von Krawczynski <skraw@ithnet.com>
To: rwhron@earthlink.net
Cc: linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net,
torvalds@transmeta.com, andrea@suse.de
Subject: Re: VM tests on 5 recent kernels
Date: Tue, 27 Nov 2001 12:37:24 +0100 [thread overview]
Message-ID: <20011127123724.04df2308.skraw@ithnet.com> (raw)
In-Reply-To: <20011127021513.A228@earthlink.net>
In-Reply-To: <20011127021513.A228@earthlink.net>
On Tue, 27 Nov 2001 02:15:13 -0500
rwhron@earthlink.net wrote:
>
> 5 recent kernels:
>
> mtest01 Averages for 10 mtest01 runs
> -------
> mtest01 allocates and writes to 80% of virtual memory.
> Listen to mp3 sampled at 128k.
>
> mp3 on 2.4.16 skipped more than 2.4.15-pre6.
> 2.4.15-pre6 and 2.5.1-pre1 did best. (fastest time, highest mp3 play).
> 2.4.16-vm is a patch from http://surriel.com/patches/
I am pretty astonished about the differences between 2.4.16 and 2.5.1-pre1. Can
anybody point out some relevant difference between the two regarding such a
test case?
Regards,
Stephan
next prev parent reply other threads:[~2001-11-27 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 7:15 VM tests on 5 recent kernels rwhron
2001-11-27 11:37 ` Stephan von Krawczynski [this message]
2001-11-27 16:58 ` Linus Torvalds
2001-11-28 1:15 ` rwhron
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=20011127123724.04df2308.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=rwhron@earthlink.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