From: Willem Riede <wriede@home.com>
To: Jussi Laako <jussi.laako@kolumbus.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux and 760MP
Date: Sat, 06 Oct 2001 10:21:13 -0400 [thread overview]
Message-ID: <3BBF1359.2020305@home.com> (raw)
In-Reply-To: <E15pdJC-0007ow-00@the-village.bc.nu>
Alan Cox wrote:
>>Alan Cox wrote:
>>
>>>memory the production ones have a couple of IDE errata (performance and
>>>can't enable prefetching) and an APIC one
>>>
>>Is there workaround for these in recent -ac kernels? So is it safe to buy
>>Tyan Tiger MP for example?
>>
>
>Nothing should be needed. If it is then running "noapic" is going to cure
>it.
>-
>
I've got my Tyan Tiger MP up now for about a week, running a 2.4.9-ac18
kernel with
some of the patches from Red Hat's Rawhide kernel rpm applied, and I've
not needed
"noapic" and it's been perfectly stable. I'm not through testing or
optimizing performance
though, but so far so good.
Willem Riede.
prev parent reply other threads:[~2001-10-06 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 13:01 Linux and 760MP Trever L. Adams
2001-10-05 14:42 ` Alan Cox
2001-10-05 21:09 ` Jussi Laako
2001-10-05 22:19 ` Alan Cox
2001-10-06 14:21 ` Willem Riede [this message]
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=3BBF1359.2020305@home.com \
--to=wriede@home.com \
--cc=jussi.laako@kolumbus.fi \
--cc=linux-kernel@vger.kernel.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