On Fri, 14 Oct 2011, Satoru Moriya wrote: > > Satoru was specifically talking about the VM using free memory for > > pagecache, > > Yes, because we can't stop increasing pagecache and it > occupies RAM where some people want to keep free for bursty > memory requirement. Usually it works fine but sometimes like > my test case doesn't work well. > > > so doing echo echo 1 > /proc/sys/vm/drop_caches can mitigate > > that almost immediately. > > I know it and some admins use that kind of tuning. But is it > proper way? Should we exec the script like above periodically? > I believe that we should use it for debug only. > Agreed, this was in response to the suggestion for adding a mem_shrink() syscall, which would require the same periodic calls or knowledge of the application prior to the bursty memory allocations. I bring up drop_caches just to illustrate that it is effectively the same thing for the entire address space when pressured by pagecache. So I don't think that syscall would actually help for your scenario. > > If there were a change to increase the space significantly between the > > high and min watermark when min_free_kbytes changes, that would fix the > > problem. > > Right. But min_free_kbytes changes both thresholds, foregroud reclaim > and background reclaim. I'd like to configure them separately like > dirty_bytes and dirty_background_bytes for flexibility. > The point I'm trying to make is that if kswapd can be made aware that it was kicked by a rt_task() in the page allocator, the same criteria we use for ALLOC_HARDER today, or a rt_task() subsequently enters the page allocator slowpath while kswapd is running, then not only can we increase the scheduling priority of kswapd but it is also possible to reclaim above the high watermark for an extra bonus. I believe we can find a sane middle ground that requires no userspace tunable where a _single_ realtime application cannot allocate memory faster than kswapd with very high priority and reclaiming above the high watermark, whether that's a factor of 1.25 or not. > > The problem is two-fold: that comes at a penalty for systems > > or workloads that don't need to reclaim the additional memory, and it's > > not clear how much space should exist between those watermarks. > > The required size depends on a system architacture such as kernel, > applications, storage etc. and so admin who care the whole system > should configure it based on tests by his own risk. > Doing that comes at a penalty for other workloads that are running on the same system, which is the problem with a global tunable that doesn't discriminate on an allocator's priority (the min -> high watermarks for reclaim do well except for rt-threads, as evidenced by this thread). -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>