> -----Original Message----- > From: ext David Rientjes [mailto:rientjes@xxxxxxxxxx] > Sent: 09 January, 2012 12:09 ... > > I'm not sure why you need to detect low memory thresholds if you're not > interested in using the memory controller, why not just use the oom killer > delay that I suggested earlier and allow userspace to respond to conditions > when you are known to failed reclaim and require that something be killed? As I understand that is required to turn on memcg and memcg is a thing I try to avoid. > > 1.7. David Rientjes > > > This is just a side-note but as this information is meant to be > > > consumed by userspace you have the option of hooking into the > > > mm_page_alloc tracepoint. You get the same information about how > > > many pages are allocated or freed. I accept that it will probably be a bit > slower but on the plus side it'll be backwards compatible and you don't need > a kernel patch for it. > > > > I didn't write that. Sorry, it was Mel Gorman. Copy-paste problem. -- 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