From: Val Henson <val@nmt.edu>
To: Christopher Murtagh <christopher.murtagh@mcgill.ca>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Highmem on PPC?
Date: Thu, 7 Feb 2002 23:25:57 -0700 [thread overview]
Message-ID: <20020207232557.B22964@boardwalk> (raw)
In-Reply-To: <Pine.LNX.4.33.0202080101000.9080-100000@blues.wcg.mcgill.ca>; from christopher.murtagh@mcgill.ca on Fri, Feb 08, 2002 at 01:05:23AM -0500
On Fri, Feb 08, 2002 at 01:05:23AM -0500, Christopher Murtagh wrote:
>
> On Thu, 7 Feb 2002, Val Henson wrote:
> >Also, I don't think this was a particularly good test of highmem since I
> >don't think many bounce buffers were used, or that the kernel had much
> >reason to map/unmap many highmem pages. Unfortunately, my SCSI
> >controller isn't working quite right and I can't test with a hard disk
> >as a result. Any ideas for stressing the system harder?
>
> My Dual800 ran fine for well over a week in my office with 1GB of RAM and
> with SMP. It also ran with a load average of around 10 for a couple of
> hours when I tried to stress test it. It was only when it started getting
> a bit of network traffic after moving it into our machine room did it
> crash, and then it crashed often. (It was also compiled with GMAC and BMAC
> network drivers).
>
> So, don't know if this info helps or not, but I'd say try giving it a
> network stress test as well as a heavy CPU load. Once I turned off SMP, it
> seems to be very stable (still with 1 GB of RAM).
Thanks for the suggestion, but I was doing all that work on an NFS
mounted root in addition to the two flood pings. :) I think the
network was being stressed quite well.
-VAL
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-08 6:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 1:32 Highmem on PPC? Val Henson
2002-02-05 12:52 ` benh
2002-02-05 18:56 ` Val Henson
2002-02-05 19:33 ` Benjamin Herrenschmidt
2002-02-05 19:42 ` Val Henson
2002-02-05 19:47 ` Benjamin Herrenschmidt
2002-02-07 12:27 ` Christopher Murtagh
2002-02-07 21:43 ` Val Henson
2002-02-07 21:51 ` Benjamin Herrenschmidt
2002-02-07 21:56 ` Val Henson
2002-02-07 21:59 ` Benjamin Herrenschmidt
2002-02-07 21:53 ` Mark A. Greer
2002-02-07 21:58 ` Val Henson
2002-02-07 23:09 ` Mark A. Greer
2002-02-08 3:02 ` Tom Rini
2002-02-08 6:05 ` Christopher Murtagh
2002-02-08 6:25 ` Val Henson [this message]
2002-02-08 17:36 ` Val Henson
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=20020207232557.B22964@boardwalk \
--to=val@nmt.edu \
--cc=benh@kernel.crashing.org \
--cc=christopher.murtagh@mcgill.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.