[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1409231523320.22630@chino.kir.corp.google.com>
Date: Tue, 23 Sep 2014 15:24:30 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: 朱辉 <zhuhui@...omi.com>
cc: Weijie Yang <weijie.yang.kh@...il.com>,
Greg KH <gregkh@...uxfoundation.org>,
"vinayakm.list@...il.com" <vinayakm.list@...il.com>,
"weijie.yang@...sung.com" <weijie.yang@...sung.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"teawater@...il.com" <teawater@...il.com>
Subject: Re: [PATCH] Fix the issue that lowmemkiller fell into a cycle that
try to kill a task
On Tue, 23 Sep 2014, 朱辉 wrote:
> > By the way, whether we need to modify out_of_memory() which also
> > try to kill task?
>
> I am not sure because LMK handle the memory issue early than OOM.
> But I think this issue will not affect OOM because OOM has oom_zonelist_trylock and oom_zonelist_unlock.
>
The oom killer tries to schedule other processes that exit the oom killer
without being a victim itself and any process that cannot get the zonelist
lock will do the same in the page allocator. The low memory killer case
is somewhat different.
Powered by blists - more mailing lists