>> 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.
> 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.
On 2016/5/31 22:03, Michal Hocko wrote:
On Tue 31-05-16 13:35:37, zhouxianrong wrote:
Hey :
the consideration of this patch is that reusing mapping page
rather than allocating a new page for page cache when system be
placed in some states. For lookup pages quickly add a new tag
PAGECACHE_TAG_REUSE for radix tree which tag the pages that is
suitable for reusing.
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?
[...]
How to startup the functional
1. the system is under low memory state and there are fs rw operations
2. page cache size is get bigger over sysctl limit
So is this a form of a page cache limit to trigger the reclaim earlier
than on the global memory pressure?
--
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
