public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net
Subject: VM test on 2.4.14pre3aa2 (compared to 2.4.14pre3aa1)
Date: Sun, 28 Oct 2001 12:07:21 -0500	[thread overview]
Message-ID: <20011028120721.A286@earthlink.net> (raw)


Summary:	2.4.14pre3aa2 gave oom errors not seen in 2.4.14pre3aa1.

Test:	Usual scripts to execute mtest01 and mmap001.  
	Listen to long mp3 with mp3blaster.

mtest01 -p 80 -w
================

2.4.14pre3aa1

Averages for 10 mtest01 runs
bytes allocated:                    1246232576
User time (seconds):                2.105
System time (seconds):              2.773
Elapsed (wall clock) time:          59.503
Percent of CPU this job got:        7.80
Major (requiring I/O) page faults:  132.8
Minor (reclaiming a frame) faults:  305043.1

2.4.14pre3aa2

Averages for 10 mtest01 runs
bytes allocated:                    1254201753
User time (seconds):                2.211
System time (seconds):              2.794
Elapsed (wall clock) time:          65.176
Percent of CPU this job got:        7.20
Major (requiring I/O) page faults:  129.7
Minor (reclaiming a frame) faults:  306988.9


mmap001 -m 500000
=================

This test worked on 2.4.14pre3aa1, but on 2.4.14pre3aa2, each
iteration was terminated by signal 9.  Also an irc client I
had running was killed.  

/var/log/kern.log had these messages:

Oct 28 11:50:24 rushmore kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Oct 28 11:50:24 rushmore kernel: VM: killing process mmap001
Oct 28 11:51:07 rushmore kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Oct 28 11:51:07 rushmore kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Oct 28 11:51:08 rushmore last message repeated 3 times
Oct 28 11:51:08 rushmore kernel: VM: killing process bx
Oct 28 11:51:09 rushmore kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Oct 28 11:51:12 rushmore kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Oct 28 11:51:13 rushmore last message repeated 2 times
Oct 28 11:51:13 rushmore kernel: VM: killing process mmap001
Oct 28 11:51:47 rushmore kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Oct 28 11:51:47 rushmore kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Oct 28 11:51:47 rushmore kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Oct 28 11:51:47 rushmore kernel: VM: killing process mmap001


Hardware:
AMD Athlon 1333
512 MB RAM
1024 MB swap.

-- 
Randy Hron


             reply	other threads:[~2001-10-28 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-28 17:07 rwhron [this message]
2001-10-29  0:47 ` VM test on 2.4.14pre3aa2 (compared to 2.4.14pre3aa1) Andrea Arcangeli
2001-10-29  2:45   ` Andrea Arcangeli
2001-10-29  3:29     ` Andrea Arcangeli
2001-10-29  3:57       ` 2.4.14pre3aa3 [was Re: VM test on 2.4.14pre3aa2 (compared to 2.4.14pre3aa1)] Andrea Arcangeli
2001-10-30  0:10         ` rwhron
2001-10-29  4:24       ` VM test on 2.4.14pre3aa2 (compared to 2.4.14pre3aa1) Linus Torvalds

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=20011028120721.A286@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