From: Sha Zhengju <handai.szj@gmail.com>
To: Ni zhan Chen <nizhan.chen@gmail.com>
Cc: linux-mm@kvack.org, cgroups@vger.kernel.org,
kamezawa.hiroyu@jp.fujitsu.com, akpm@linux-foundation.org,
mhocko@suse.cz, linux-kernel@vger.kernel.org,
Sha Zhengju <handai.szj@taobao.com>
Subject: Re: [PATCH] oom, memcg: handle sysctl oom_kill_allocating_task while memcg oom happening
Date: Tue, 16 Oct 2012 18:41:41 +0800 [thread overview]
Message-ID: <507D39E5.5010301@gmail.com> (raw)
In-Reply-To: <507D34E3.3040705@gmail.com>
On 10/16/2012 06:20 PM, Ni zhan Chen wrote:
> On 10/16/2012 06:12 PM, Sha Zhengju wrote:
>> From: Sha Zhengju <handai.szj@taobao.com>
>>
>> Sysctl oom_kill_allocating_task enables or disables killing the
>> OOM-triggering
>> task in out-of-memory situations, but it only works on overall
>> system-wide oom.
>> But it's also a useful indication in memcg so we take it into
>> consideration
>> while oom happening in memcg. Other sysctl such as panic_on_oom has
>> already
>> been memcg-ware.
>
> Is it the resend one or new version, could you add changelog if it is
> the last case?
Sorry, forget to mention that this patch is an updated one rebased on
mhocko mm tree, since-3.6 branch.
The first one is on old kernel, please ignore it. :-)
Thanks,
Sha
next prev parent reply other threads:[~2012-10-16 10:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 10:12 [PATCH] oom, memcg: handle sysctl oom_kill_allocating_task while memcg oom happening Sha Zhengju
2012-10-16 10:20 ` Ni zhan Chen
2012-10-16 10:41 ` Sha Zhengju [this message]
2012-10-16 13:34 ` Michal Hocko
2012-10-16 18:39 ` David Rientjes
[not found] ` <CAFj3OHVW-betpEnauzk-vQEfw_7bJxFneQb2oWpAZzOpZuMDiQ@mail.gmail.com>
2012-10-18 11:56 ` Michal Hocko
2012-10-18 13:51 ` Sha Zhengju
2012-10-18 15:32 ` Michal Hocko
2012-10-19 4:11 ` Sha Zhengju
2012-10-19 9:52 ` Michal Hocko
2012-10-16 18:44 ` David Rientjes
-- strict thread matches above, loose matches on Subject: below --
2012-10-16 6:10 Sha Zhengju
2012-10-16 6:12 ` David Rientjes
2012-10-16 6:32 ` Sha Zhengju
2012-10-16 7:03 ` Michal Hocko
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=507D39E5.5010301@gmail.com \
--to=handai.szj@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=handai.szj@taobao.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=nizhan.chen@gmail.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