> One argument for reverse mappings is distributed shared memory or
> distributed file systems and their interaction with memory mapped
> files. For example, a distributed file system may need to invalidate a specific
> page of a file that may be mapped multiple times on a node.
To reduce the time for an invalidate is indeed a good argument for
reverse maps. However this is generally the uncommon case, and it is
fine to leave this kinds of things on the slow path. From struct page
we currently go to struct address_space to lists of struct vm_area
which works but is just a little slower (but generally cheaper) than
having a reverse map.
Since Rik was not seeing the invalidate or the unmap case as the
bottleneck this reverse mappings are not needed simply something
with a similiar effect on the VM.
In linux we have avoided reverse maps (unlike the BSD's) which tends
to make the common case fast at the expense of making it more
difficult to handle times when the VM system is under extreme load and
we are swapping etc.
Eric
-
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/