On Thu, Jan 25, 2001 at 03:58:37AM +0000, Charles M. Hannum wrote:

 > There are other calls to uvm_pagedeactivate() which may be affected by
 > making it not call pmap_clear_reference().  It seems pretty clear that
 > just removing the pmap_clear_reference() there is going to cause them
 > to deactivate the page and then immediately reactivate it because the
 > bit is still set.  So, it may be necessary to adjust those callers to
 > avoid doing an extra pmap_clear_reference() in the page scanner.

Hm, I don't think I ever suggested taking the clear_reference out of
uvm_pagedeactivate().  Indeed, it should stay there, IMO.

-- 
        -- Jason R. Thorpe <thorpej@zembu.com>