Messages in this thread | | | Date | Wed, 14 Jan 2009 16:12:24 -0800 | From | Greg KH <> | Subject | Re: lowmemory android driver not needed? |
| |
On Wed, Jan 14, 2009 at 03:32:38PM -0800, Arve Hjønnevåg wrote: > On Wed, Jan 14, 2009 at 3:17 PM, Greg KH <greg@kroah.com> wrote: > >> We actually use 6 different thresholds for killing processes. I don't > >> know what all the classes are, processes with a higher oom_adj value > >> can be killed with less impact to the user than processes with a lower > >> oom_adj value. The first few classes only affect latency when > >> switching apps, but later classes stop non critical background > >> services and finally the foreground app. Another reason to not kill > >> every process at the same threshold is that memory may not be free > >> immediately when the process is killed. > > > > But the lowmemorykiller android module doesn't have anything to do with > > this, right? > > > > It does. We write the thresholds to > /sys/module/lowmemorykiller/parameters/adj and > /sys/module/lowmemorykiller/parameters/minfree then set the oom_adj > value per process. If the standard oom killer can be adjusted in a > similar way, then we will not need the lowmemorykiller module.
Great, care to document this somewhere so people like me don't get confused?
thanks,
greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |