On 06/08/2012 08:14 PM, Anton Vorontsov wrote: > On Fri, Jun 08, 2012 at 07:42:04PM +0900, Minchan Kim wrote: > [...] >> I can't understand. Why can't the approach catch the situation? >> Let's think about it. >> >> There is 40M in CleanCache LRU which has easy-reclaimable pages and >> there is 10M free pages and 5M high watermark in system. >> >> Your application start to consume free pages very slowly. >> So when your application consumed 5M, VM start to reclaim. So far, it's okay >> because we have 40M easy-reclaimable pages. And low memory notifier can start >> to notify so your dameon can do some action to get free pages. > > Maybe I'm missing how would you use the shrinker. But the last time > I tried on my (swap-less, FWIW) qemu test setup, I was not receiving > any notifications from the shrinker until the system was almost > (but not exactly) out of memory. > > My test app was allocating all memory MB by MB, filling the memory > with zeroes. So, what I was observing is that shrinker callback was > called just a few MB before OOM, not every 'X' consumed MBs. Yes. page reclaimer doesn't make sure calling shrinker per MB. So if you want to be notified per your threshold, shrinker isn't good. I didn't say I will use shrinker. I want to add hooks directly in vmscan.c's normal reclaim path, not shrinker. Still, I want to implement it by level triggering like I mentioned. I will show you my concept if anybody doesn't interrupt me within a few weeks. :) Thanks. > >> I think it's not so late. >> >> sidenote: >> It seems I live in the complete opposite place because >> you guys always start discussion when I am about going out of office. >> Please understand my late response. >> Maybe I will come back after weekend. :) > > Well, it's 4AM here. :-) Have a great weekend! > You win! :) -- Kind regards, Minchan Kim -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>