Re: Implement lookup_swap_cache for migration entries

[Christoph Lameter <clameter@sgi.com>]

On Fri, 14 Apr 2006, Andrew Morton wrote:

> > > What locking ensures that the state of `entry' remains unaltered across the
> > > is_migration_entry() and migration_entry_to_page() calls?
> > 
> > entry is a variable passed by value to the function.
> 
> Sigh.
> 
> What locking ensures that the state of the page referred to by `entry' is
> stable?

Oh, that.

Well, there is no locking when retrieving a pte atomically from the page 
table. In do_swap_cache we figure out the page from the pte, lock the page 
and then check that the pte has not changed. If it has changed then we 
redo the fault. If the pte is still the same then we know that the page 
was stable in the sense that it is still mapped the same way. So it was 
not freed.

This applies to all pages handled by do_swap_page().

The differences are:

1. A migration entry does not take the tree_lock in lookup_swap_cache().

2. The migration thread will restore the regular pte before 
   dropping the page lock.

So after we succeed with the page lock we know that the pte has been 
changed. The fault will be redone with the regular pte.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>