On 01/28/2011 02:45 PM, Andrea Arcangeli wrote:
On Fri, Jan 28, 2011 at 02:34:31PM -0500, Rik van Riel wrote:
It will block at high+gap only when one zone has really
easily reclaimable memory, and another zone has difficult
to free memory.
The other zone doesn't need to be difficult to free up. All ram in
immediately freeable clean cache is the most common case there is. And
it's more than enough to trigger the scenario in prev email.
That creates a free memory differential between the
easy to free and difficult to free memory zones.
There's no difficult to free zone in this scenario.
In that case, every zone will go down to the low watermark
before kswapd is woken up.
At that point, kswapd will reclaim until every zone is at
the high watermark, and go back to sleep.
There is no "free up to high + gap" in your scenario.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>