Re: [patch 3/9] Guest page hinting: volatile page cache.

[Dave Hansen <haveblue@us.ibm.com>]

On Fri, 2006-09-01 at 18:04 +0200, Martin Schwidefsky wrote:
> 3) The page-has-a-writable-mapping (PG_writable) bit is set when the
> first writable pte for a page is established. The page needs to have a
> different state if a writable pte exists compared to a read-only page.
> The alternative without the page bit would be to do the state change
> every time a writable pte is established or to search all ptes of a
> given page. Both have performance implications.  

What are the performance implications?  Do they completely erase any
performance gains that these patches might have given in the first
place?  Has there been any evaluation of these other two alternatives?
As I understand it, carrying out this performance analysis would be very
difficult for most of the kernel community to perform.

Keeping a nice count of the number of writable PTEs sounds like
something that might be generally useful.  Could we split
page->_mapcount to keep track of r/o and r/w ptes separately?  Or,
perhaps a single bit in it can be utilized to replace PG_writable,
instead.

-- Dave

-
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/