public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [Semi-OT] Dual Athlon support in kernel
Date: Tue, 24 Apr 2001 03:33:00 -0400	[thread overview]
Message-ID: <3AE52C2C.C6B2B472@mountain.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0104240115050.21785-100000@asdf.capslock.lan>

"Mike A. Harris" wrote:
> 
> Would the current state of athlon support be considered stable?
> I've got a colleague interested in getting a dual athlon box, and
> I'll be making the decision as to what hardware to purchase.  I'm
> wondering is dual Athlon viable for a business solution right
> now, or is it considered "experimental"?
> 
> What hardware would be recommended for a dual CPU system that
> needs to be fairly rock solid?  Should I recommend to stay with
> the P-III Xeon?  Or something else?  What issues would I expect
> to have to deal with if going with a dual Athlon?
> 
> Also, what is a good rock solid SCSI RAID controller?  Money is
> no object.  Reliability, performance and Linux compatibility are
> though.
> 
> Chipsets to avoid?
> 
> Any experiences/info good/bad would be greatly appreciated.

The build problen with Athlon+SMP was solved by AA's patch. I had tested a
similar patch on UP over 2.4.0-test and previous 2.4 releases with nary a
problem.

This may be too experimental for your purposes, but FWIW I'm writing from a
2.4.4-pre3 built with gcc-2.97-20010205 using -march=athlon set by the k7
config. I've been building kernels with that snapshot since the middle of
Feb. With the current image, the box has locked up once in continuous use. I
can't say what caused that one, no log survived. 

Cheers,
Tom

-- 
The Daemons lurk and are dumb. -- Emerson

  parent reply	other threads:[~2001-04-24  7:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24  5:22 [Semi-OT] Dual Athlon support in kernel Mike A. Harris
2001-04-24  6:05 ` Andrea Arcangeli
2001-04-24  7:33 ` Tom Leete [this message]
2001-04-24 10:18   ` Ville Herva
2001-04-24 10:39     ` Joseph Carter
2001-04-24 10:55       ` [Fully-OT] " Ville Herva
2001-04-24 11:11       ` [Semi-OT] " Andreas Jaeger
2001-04-24 23:18 ` Martin Clausen
2001-04-26 23:01   ` Jakob Østergaard
  -- strict thread matches above, loose matches on Subject: below --
2001-04-24  6:03 Antwerpen, Oliver
2001-04-24  6:15 ` Andrea Arcangeli
2001-04-24  6:30   ` Miles Lane
2001-04-24  6:22 Antwerpen, Oliver

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=3AE52C2C.C6B2B472@mountain.net \
    --to=tleete@mountain.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharris@opensourceadvocate.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