Re: [PATCH] mm: tracking dirty pages -v6

If this one still has some problems there is on more thing we could try
before going back to the old way of doing things.

I found this 'gem' in the drm code:

        vma->vm_page_prot =
            __pgprot(pte_val
                     (pte_wrprotect
                      (__pte(pgprot_val(vma->vm_page_prot)))));

which does exactly what is needed.

OTOH, my alternate version of the mprotect fix leaves dirty pages
writable, which saves a few faults.

Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 0/3] mm: tracking dirty pages -v5
    • From: Peter Zijlstra <[email protected]>
  • Re: [PATCH 0/3] mm: tracking dirty pages -v5
    • From: Hugh Dickins <[email protected]>
  • [PATCH] mm: tracking dirty pages -v6
    • From: Peter Zijlstra <[email protected]>

• Prev by Date: Re: 2.6.17-rc6-mm1
• Next by Date: Re: adaptive readahead overheads
• Previous by thread: [PATCH] mm: tracking dirty pages -v6
• Next by thread: Re: [PATCH] mm: tracking dirty pages -v6
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]