Re: VM tuning patch, take 2

[Jonathan Morton <chromi@cyberspace.org>]

>> - new pages are still given an age of PAGE_AGE_START, which is 2.
>> PAGE_AGE_ADV has been increased to 4, and PAGE_AGE_MAX to 128.  Pages which
>> are demand-paged in from swap are given an initial age of PAGE_AGE_MAX/2,
>> or 64 - this should help to keep these (expensive) pages around for as long
>> as possible.  Ageing down is now done using a decrement instead of a
>> division by 2, preserving the age information for longer.
>
>Just one comment about this specific change. I would not like to tweak the
>PAGE_AGE_* values until we have centralized page aging. (ie only kswapd
>doing the aging)

I forgot to mention, I also have applied the patch which causes allocations
to wait on kswapd.  As far as I can tell, the actual numbers attached to
the ageing matter far less than how they are applied.

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@cyberspace.org  (not for attachments)

The key to knowledge is not to rely on people to teach you it.

GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/