> > [...] or to do the clearing (and copying) speculatively, after
> > allocating the page but before locking the pagetable lock. This might
> > lead to a bit more work in the pagefault-race case, but we dont care
> > about that window. It will on the other hand reduce pagetable_lock
> > contention (because the clearing/copying is done outside the lock), so
> > perhaps this solution is better.
>
> the attached highmem-2.4.7-A0 patch implements this method in both
> affected functions. Comments?
It seems to me that the problem is more fundamental than that. Excuse my
ignorance, but what keeps the 'old_page' (and associated pte, checked two
lines down) from disappearing somewhere between the lock drop, alloc page
and the copy from the old page? Normally if this happens it appears the new
page gets dropped and the fault occurs again, and is resolved in a
potentially different way.
jlinton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 21:00:29 EST