From: Tom Rini <trini@kernel•crashing.org>
To: Val Henson <val@nmt•edu>
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: Highmem on PPC?
Date: Thu, 7 Feb 2002 20:02:27 -0700 [thread overview]
Message-ID: <20020208030227.GA15584@opus.bloom.county> (raw)
In-Reply-To: <20020207144308.C19569@boardwalk>
On Thu, Feb 07, 2002 at 02:43:08PM -0700, Val Henson wrote:
>
> On Tue, Feb 05, 2002 at 08:33:16PM +0100, Benjamin Herrenschmidt wrote:
> >
> > And let me know if you find something ;)
>
> I pulled the latest linuxppc_2_4_devel, ported gemini to it, and ran
> an overnight test with:
>
> NFS mounted root filesystem
> while (true) do make clean; make -j8 zImage; done
> crashme +2000 666 100 8:00:00 2
> Flood ping in and out
>
> On a dual 7410 Gemini with 1 GB RAM. Used all but 70MB of memory. No
> hangs.
>
> The weird thing is that crashme was supposed to run for 8 hours but
> it's been running for over 14 hours now. Any ideas?
Hmm. Have you tried timing some 'simple' things and seeing if thats
correct?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-08 3:02 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 [this message]
2002-02-08 6:05 ` Christopher Murtagh
2002-02-08 6:25 ` Val Henson
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=20020208030227.GA15584@opus.bloom.county \
--to=trini@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=val@nmt$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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