On 03/05/2018 12:20 PM, Dave Hansen wrote:
On 02/21/2018 09:15 AM, Khalid Aziz wrote:
If a processor supports special metadata for a page, for example ADI
version tags on SPARC M7, this metadata must be saved when the page is
swapped out. The same metadata must be restored when the page is swapped
back in. This patch adds two new architecture specific functions -
arch_do_swap_page() to be called when a page is swapped in, and
arch_unmap_one() to be called when a page is being unmapped for swap
out. These architecture hooks allow page metadata to be saved if the
architecture supports it.
I still think silently squishing cacheline-level hardware data into
page-level software data structures is dangerous.
But, you seem rather determined to do it this way. I don't think this
will _hurt_ anyone else, though other than needlessly cluttering up the
code.
Hello Dave,
Thanks for taking the time to look at this patch and providing feedback.
ADI data is per page data and is held in the spare bits in the RAM. It
is loaded into the cache when data is loaded from RAM and flushed out to
spare bits in the RAM when data is flushed from cache. Sparc allows one
tag for each ADI block size of data and ADI block size is same as
cacheline size. When a page is loaded into RAM from swap space, all of
the associated ADI data for the page must also be loaded into the RAM,
so it looks like page level data and storing it in page level software
data structure makes sense. I am open to other suggestions though.
Thanks,
Khalid
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
