From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net
Subject: ltp on 2.4.11-pre2 and 2.4.10-ac4 (athlon on ext2)
Date: Wed, 3 Oct 2001 03:44:51 -0400 [thread overview]
Message-ID: <20011003034451.A2596@earthlink.net> (raw)
Linux Test Project suite on 2.4.11-pre2 and 2.4.10-ac4.
This isn't a duplicate. This machine recently had reiserfs errors
during LTP. Here are tests with ext2. (I'm re-running ltp on reiserfs too)
Kernel versions: 2.4.10-ac4 and 2.4.11-pre2
kernel .config: identical
Filesystem: ext2
Distro: Linux From Scratch 3.0
glibc: 2.2.4
LTP version: 20010925
Hardware:
AMD Athlon 1333 mhz
IWill KK266 motherboard
512 megs RAM
1024 megs swap
Test process:
boot kernel
login 3 console ttys
run "vmstat 8 >logfile" and tail it
run "for" loop to repeat LTP 3 times and log results
tail -f LTP results files
light use of links and irc clients.
no X.
There was a PASS for 10670 to 10676 tests.
LTP isn't a benchmark, but here are some growfile i/o results:
Linux rushmore 2.4.10-ac4 941824 iterations on 41 files in 760 seconds
Linux rushmore 2.4.10-ac4 939209 iterations on 41 files in 760 seconds
Linux rushmore 2.4.10-ac4 932649 iterations on 41 files in 760 seconds
Linux rushmore 2.4.11-pre2 914028 iterations on 41 files in 760 seconds
Linux rushmore 2.4.11-pre2 920055 iterations on 41 files in 760 seconds
Linux rushmore 2.4.11-pre2 924409 iterations on 41 files in 760 seconds
All growfiles commands completed successfully!
Unique test PASS
1st 2.4.11-pre2 run
recv01 3 PASS : invalid recv buffer successful
Unique test failures
1st 2.4.10-ac4
nanosleep02 1 FAIL : Child execution not suspended for 5 seconds
nanosleep02 1 FAIL : child process exited abnormally
vmstat steady state after the three runs:
2.4.10-ac4
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 0 0 266620 68132 157876 11848 0 0 0 0 104 71 0 0 100
2.4.11-pre2
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 0 0 12808 483932 2188 14368 1 0 1 0 103 71 0 0 100
That is a snippet from the logfile after 3 runs completed. It is not
the result of a single iteration of "vmstat".
Here are some earlier results that were not using the same .config file.
In these tests I was playing mp3's, running top, ps, etc watching what
the tests do. These were all with reiserfs.
Linux rushmore 2.4.9-ac10 756999 iterations on 41 files in 760 seconds
Linux rushmore 2.4.9-ac10 903693 iterations on 41 files in 760 seconds
Linux rushmore 2.4.9-ac10 910502 iterations on 41 files in 760 seconds
Linux rushmore 2.4.9-ac17 728331 iterations on 41 files in 760 seconds
Linux rushmore 2.4.9-ac17 899508 iterations on 41 files in 760 seconds
Linux rushmore 2.4.9-ac17 903786 iterations on 41 files in 760 seconds
Linux rushmore 2.4.9-ac17 908911 iterations on 41 files in 760 seconds
Linux rushmore 2.4.9-ac17 914780 iterations on 41 files in 760 seconds
Linux rushmore 2.4.9-ac18 907163 iterations on 41 files in 760 seconds
--
Randy Hron
Linux News at http://lwn.net/
--
Randy Hron
= Linux - because it's all about freedom =
Linux News at http://lwn.net/
reply other threads:[~2001-10-03 7:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011003034451.A2596@earthlink.net \
--to=rwhron@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
/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