Messages in this thread | | | From | Suren Baghdasaryan <> | Date | Thu, 11 Apr 2019 09:54:09 -0700 | Subject | Re: [Lsf-pc] [RFC 0/2] opportunistic memory reclaim of a killed process |
| |
On Thu, Apr 11, 2019 at 5:16 AM Michal Hocko <mhocko@kernel.org> wrote: > > On Thu 11-04-19 07:51:21, Rik van Riel wrote: > > On Wed, 2019-04-10 at 18:43 -0700, Suren Baghdasaryan via Lsf-pc wrote: > > > The time to kill a process and free its memory can be critical when > > > the > > > killing was done to prevent memory shortages affecting system > > > responsiveness. > > > > The OOM killer is fickle, and often takes a fairly > > long time to trigger. Speeding up what happens after > > that seems like the wrong thing to optimize. > > > > Have you considered using something like oomd to > > proactively kill tasks when memory gets low, so > > you do not have to wait for an OOM kill? > > AFAIU, this is the point here. They probably have a user space OOM > killer implementation and want to achieve killing to be as swift as > possible.
That is correct. Android has a userspace daemon called lmkd (low memory killer daemon) to respond to memory pressure before things get bad enough for kernel oom-killer to get involved. So this asynchronous reclaim optimization would allow lmkd do its job more efficiently.
> -- > Michal Hocko > SUSE Labs > > -- > You received this message because you are subscribed to the Google Groups "kernel-team" group. > To unsubscribe from this group and stop receiving emails from it, send an email to kernel-team+unsubscribe@android.com. >
| |