Daniel Phillips wrote:
>
> > ...
> We do get
> around to walking the ptes at file close I believe. Is that not driven by
> zap_page_range, which moves any orphaned pte dirty bits down into the struct
> page?
Nope, close will just leave all the pages pte-dirty or PageDirty in
memory. truncate will nuke all the ptes and then the pagecache.
But the normal way in which pte-dirty pages find their way to the
backing file is:
- page reclaim runs try_to_unmap or
- user runs msync(). (Which will only clean that mm's ptes!)
These will run set_page_dirty(), making the page visible to
one of the many things which run writeback.
-
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/
This archive was generated by hypermail 2b29 : Sun Sep 15 2002 - 22:00:23 EST