On Fri, 16 Feb 2001, Manfred Spraul wrote: > That leaves msync() - it currently does a flush_tlb_page() for every > single dirty page. > Is it possible to integrate that into the mmu gather code? > > tlb_transfer_dirty() in addition to tlb_clear_page()? Actually, in the filemap_sync case, the flush_tlb_page is redundant -- there's already a call to flush_tlb_range in filemap_sync after the dirty bits are cleared. None of the cpus we support document having a writeback tlb, and intel's docs explicitely state that they do not as they state that the dirty bit is updated on the first write to dirty the pte. -ben - 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/
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Linus Torvalds
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Ben LaHaise
- Re: x86 ptep_get_and_clear question Linus Torvalds
- Re: x86 ptep_get_and_clear question Ben LaHaise
- Re: x86 ptep_get_and_clear question Linus Torvalds
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Hugh Dickins
- Re: x86 ptep_get_and_clear question Ben LaHaise
- Re: x86 ptep_get_and_clear question Linus Torvalds
- Re: x86 ptep_get_and_clear question Ben LaHaise