mm: tracking dirty pages -v8
Get series with b4
b4 am 20060613112120.27913.71986.sendpatchset@lappyVersions newest first
- v1 Latest6 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | mm: tracking shared dirty pagesfs/ include/ include/ +5 more | +177 | 3 replies | |
| 2/6 | mm: balance dirty pagesinclude/ mm/ mm/ | +14 | 0 replies | |
| 3/6 | mm: msync() cleanupmm/ | +9 | 0 replies | |
| 4/6 | mm: optimize the new mprotect() code a bitmm/ | +23 | 0 replies | |
| 5/6 | mm: small cleanup of install_page()mm/ | +2 | 0 replies | |
| 6/6 | mm: remove some update_mmu_cache() callsmm/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] mm: tracking dirty pages -v8
The latest version of the tracking dirty pages patch-set.
This version handles VM_PFNMAP vmas and the COW case of shared RO mappings.
follow_page() got a comment for being weird, but in the light of the set_page_dirty() call that can not yet be removed does something sane.
copy_one_pte() also does the right thing, although I wonder why it clears the dirty bit for children?
f_op->open() - sets a backing_dev_infof_op->mmap() - modifies both vma->vm_flags and vma->vm_page_prot
Since our condition depends on both the backing_dev_info and vma->vm_flags it cannot set vma->vm_page_prot before f_op->mmap().
However this means that !VM_PFNMAP vmas that are shared writable but do not provide a f_op->nopage() and whos backing_dev_info does not have BDI_CAP_NO_ACCT_DIRTY, are left writable.
Peter
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>