From owner-freebsd-alpha Thu Jul 20 14:54:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 318B937C185 for ; Thu, 20 Jul 2000 14:54:48 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA00712; Thu, 20 Jul 2000 15:03:36 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007202203.PAA00712@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Thu, 20 Jul 2000 15:11:16 EDT." <200007201911.PAA15726@gale.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Jul 2000 15:03:36 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > WRT memory barriers on i86 -- I though that writes to device memory space > were uncachable & flushed the write buffers unless an mtrr was set > up for the region & it was made cacheable. I defer to the i86 experts.. > As for flushing writes to main memory for better device communication, > I have no clue.. The issue here is that the memory in question isn't in device space, it's in system physical memory. Typically you don't want this sort of stuff uncached, you just want to impose ordering where it actually matters. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message