From owner-freebsd-bugs  Tue Mar 30  2:39:53 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id B9D6015A58
	for <freebsd-bugs@freebsd.org>; Tue, 30 Mar 1999 02:39:44 -0800 (PST)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1)
	id 10RvvC-000198-00; Tue, 30 Mar 1999 12:39:02 +0200
From: Sheldon Hearn <sheldonh@iafrica.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: freebsd-bugs@FreeBSD.ORG, skumles@yahoo.com
Subject: Re: i386/8894 
In-reply-to: Your message of "Tue, 30 Mar 1999 16:37:33 +1000."
             <199903300637.QAA22745@godzilla.zeta.org.au> 
Date: Tue, 30 Mar 1999 12:39:02 +0200
Message-ID: <4409.922790342@axl.noc.iafrica.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



On Tue, 30 Mar 1999 16:37:33 +1000, Bruce Evans wrote:

> CPU_WT_ALLOC should have no effect on the problem, since it should
> only be used if the cpu is Cyrix or AMD.

What does "should only be used" mean? Does it mean that CPU_WT_ALLOC has
no impact on kernel operations when the CPU is not a Cyrix nor an AMD?

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message