[lkml]   [2012]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: [PATCH 3.2.0-rc1 3/3] Used Memory Meter pseudo-device module
> -----Original Message-----
> From: ext David Rientjes []
> 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.

 \ /
  Last update: 2012-01-09 11:23    [W:0.064 / U:0.792 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site