> This, unfortunately, isn't a total solution - we may sometimes need to
> modify the task's pagetables from outside the process context, eg.
> swapout (thanks to dmc for pointing this out to me ;-)). For this, we'd
> just use the existing kmap mechanism to create another mapping to use
> temporarily, and we're no worse off than before. But on the whole I
> think it wins us enough to be worthwhile.
There is absolutely no problem mapping the page tables of
another process into our own kmap space. It's just like
what the kernel does now, except that it'll be scalable
because each process has its own kmap array.
regards,
Rik
-- Bravely reimplemented by the knights who say "NIH".http://www.surriel.com/ http://distro.conectiva.com/
- 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/