From owner-freebsd-hackers  Mon Apr  7 16:04:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA21187
          for hackers-outgoing; Mon, 7 Apr 1997 16:04:44 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA21179
          for <freebsd-hackers@freebsd.org>; Mon, 7 Apr 1997 16:04:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id QAA05769; Mon, 7 Apr 1997 16:05:03 -0700 (PDT)
Message-Id: <199704072305.QAA05769@root.com>
X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol
To: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: Some insight on "dup alloc" problems..... 
In-reply-to: Your message of "Mon, 07 Apr 1997 16:55:31 EDT."
             <199704072055.QAA03948@lakes.water.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 07 Apr 1997 16:05:03 -0700
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> In that environment; do you think that call would still be helpful?
>What exactly does wbinvd() do?  I haven't stumbled across it in my
>2.1.7.1 readings...

   It does a "write back and invalidate" which flushes the internal cache
and signals the external cache to write back it's contents to main memory.
This instruction only exists on 486 and newer CPUs, however, so it is
not relevant to your situation.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project