From: Dan Burcaw <dburcaw@terrasoftsolutions.com>
To: Christopher Murtagh <christopher.murtagh@mcgill.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: SMP/HIGHMEM/7450 status ?
Date: 08 Jun 2002 18:41:25 -0600 [thread overview]
Message-ID: <1023583285.16530.17.camel@skyfox.terraplex.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0206081908120.25112-100000@blues.wcg.mcgill.ca>
Chris,
I have a dual 1GHz as my primary build box w/ HIGHMEM
(1.5GB installed).. and I have had no stability problems w/
the latest 2.4.19...
-Dan
On Sat, 2002-06-08 at 17:10, Christopher Murtagh wrote:
>
> On Thu, 6 Jun 2002 benh@kernel.crashing.org wrote:
> >Xserve uses 7455 (like newer dual G4s), which doesn't seem to exhibit
> >the problem.
>
> Does this mean that the Dual 1Ghz machines (Quicksilver) are running fine
> with HIGHMEM and SMP? Replacing the Dual 800 with one might by my only
> option, I plan on adding some services to our central machine and I'm
> worried about CPU resources. Does anyone here have one of these running?
>
> Cheers,
>
> Chris
>
> --
>
> Christopher Murtagh
> Webmaster / Sysadmin
> Web Communications Group
> McGill University
> Montreal, Quebec
> Canada
>
> Tel.: (514) 398-3122
> Fax: (514) 398-2017
>
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-09 0:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 15:51 SMP/HIGHMEM/7450 status ? Christopher Murtagh
2002-06-06 5:37 ` benh
2002-06-06 16:29 ` Christopher Murtagh
2002-06-06 6:08 ` benh
2002-06-06 17:09 ` Christopher Murtagh
2002-06-06 17:45 ` benh
2002-06-06 19:40 ` Christopher Murtagh
2002-06-07 8:23 ` Geert Uytterhoeven
2002-06-06 19:51 ` Timothy A. Seufert
2002-06-06 19:46 ` Benjamin Herrenschmidt
2002-06-08 23:10 ` Christopher Murtagh
2002-06-09 0:41 ` Dan Burcaw [this message]
2002-06-06 16:05 ` Kevin B. Hendricks
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=1023583285.16530.17.camel@skyfox.terraplex.com \
--to=dburcaw@terrasoftsolutions.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).