From owner-freebsd-smp  Fri Dec 13 23:06:25 1996
Return-Path: <owner-smp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id XAA14856
          for smp-outgoing; Fri, 13 Dec 1996 23:06:25 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA14851
          for <freebsd-smp@freebsd.org>; Fri, 13 Dec 1996 23:06:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id XAA00954; Fri, 13 Dec 1996 23:05:04 -0800 (PST)
Message-Id: <199612140705.XAA00954@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Mike Haertel <haertel@ichips.intel.com>
cc: freebsd-smp@freebsd.org
Subject: Re: some questions concerning TLB shootdowns in FreeBSD 
In-reply-to: Your message of "Wed, 11 Dec 1996 15:15:21 PST."
             <9612112315.AA58904@pdxcs078.intel.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 13 Dec 1996 23:05:04 -0800
Sender: owner-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I'm curious how/when people are doing TLB shootdowns.
>Obviously when reducing permission or unmapping pages.
>How about for manipulations of the dirty/accessed bits?
>(Does FreeBSD use these?)

   Speaking of the uni-processor case, FreeBSD does the access/modify bit
changes in the pmap_changebit() function which does a TLB flush if anything
is actually changed.

-DG

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