> Why would you want to reuse a page about which you have no idea about
> its age compared to the LRU pages which would be mostly clean as well?
> I mean this needs a deep justification!
>
pages only dirtied by rw syscall can be reused
pages dirtied by fault due to page_mkwrite or bdi-dirty-account now does not be reused
On 2016/6/1 16:18, Michal Hocko wrote:
On Wed 01-06-16 09:52:45, zhouxianrong wrote:
A page suitable for reusing within mapping is
1. clean
2. map count is zero
3. whose mapping is evictable
Those pages are trivially reclaimable so why should we tag them in a
special way?
yes, those pages can be reclaimed by reclaim procedure. i think in low memory
case for a process that doing file rw directly-reusing-mapping-page may be
a choice than alloc_page just like directly reclaim. alloc_page could failed return
due to gfp and watermark in low memory. for reusing-mapping-page procedure quickly
select a page that is be reused so introduce a tag for this purpose.
Why would you want to reuse a page about which you have no idea about
its age compared to the LRU pages which would be mostly clean as well?
I mean this needs a deep justification!
So is this a form of a page cache limit to trigger the reclaim earlier
than on the global memory pressure?
my thinking is that page cache limit trigger reuse-mapping-page. the
limit is earlier than on the global memory pressure.
reuse-mapping-page can suppress increment of page cache size and big page cache size
is one reason of low memory and fragment.
But why would you want to limit the amount of the page cache in the
first place when it should be trivially reclaimable most of the time?
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
