From: David Rientjes <rientjes@google.com>
To: 朱辉 <zhuhui@xiaomi.com>
Cc: Weijie Yang <weijie.yang.kh@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
"vinayakm.list@gmail.com" <vinayakm.list@gmail.com>,
"weijie.yang@samsung.com" <weijie.yang@samsung.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"teawater@gmail.com" <teawater@gmail.com>
Subject: Re: [PATCH] Fix the issue that lowmemkiller fell into a cycle that try to kill a task
Date: Tue, 23 Sep 2014 15:24:30 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1409231523320.22630@chino.kir.corp.google.com> (raw)
In-Reply-To: <C1476EAB93B413409890F290A20101879D8E9B@ex-mbox2>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 554 bytes --]
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.
next prev parent reply other threads:[~2014-09-23 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 2:57 Hui Zhu
2014-09-23 4:17 ` Greg KH
2014-09-23 4:48 ` 朱辉
2014-09-23 8:00 ` Weijie Yang
2014-09-23 14:28 ` 朱辉
2014-09-23 22:24 ` David Rientjes [this message]
2014-09-24 15:34 ` Rik van Riel
2014-10-14 6:51 ` 朱辉
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1409231523320.22630@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=teawater@gmail.com \
--cc=vinayakm.list@gmail.com \
--cc=weijie.yang.kh@gmail.com \
--cc=weijie.yang@samsung.com \
--cc=zhuhui@xiaomi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®