From: Sha Zhengju <handai.szj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ni zhan Chen <nizhan.chen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org,
akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
mhocko-AlSwsSmVLrQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Sha Zhengju <handai.szj-3b8fjiQLQpfQT0dZR+AlfA@public.gmane.org>
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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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-3b8fjiQLQpfQT0dZR+AlfA@public.gmane.org>
>>
>> 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
WARNING: multiple messages have this Message-ID (diff)
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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
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: 43+ 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:12 ` Sha Zhengju
2012-10-16 10:12 ` Sha Zhengju
2012-10-16 10:20 ` Ni zhan Chen
2012-10-16 10:20 ` Ni zhan Chen
[not found] ` <507D34E3.3040705-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-10-16 10:41 ` Sha Zhengju [this message]
2012-10-16 10:41 ` Sha Zhengju
2012-10-16 10:41 ` Sha Zhengju
[not found] ` <1350382328-28977-1-git-send-email-handai.szj-3b8fjiQLQpfQT0dZR+AlfA@public.gmane.org>
2012-10-16 13:34 ` Michal Hocko
2012-10-16 13:34 ` Michal Hocko
2012-10-16 13:34 ` Michal Hocko
2012-10-16 17:14 ` Sha Zhengju
[not found] ` <CAFj3OHVW-betpEnauzk-vQEfw_7bJxFneQb2oWpAZzOpZuMDiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-18 11:56 ` Michal Hocko
2012-10-18 11:56 ` Michal Hocko
2012-10-18 11:56 ` Michal Hocko
[not found] ` <20121018115640.GB24295-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2012-10-18 13:51 ` Sha Zhengju
2012-10-18 13:51 ` Sha Zhengju
2012-10-18 13:51 ` Sha Zhengju
[not found] ` <5080097D.5020501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-10-18 15:32 ` Michal Hocko
2012-10-18 15:32 ` Michal Hocko
2012-10-18 15:32 ` Michal Hocko
[not found] ` <20121018153256.GC24295-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2012-10-19 4:11 ` Sha Zhengju
2012-10-19 4:11 ` Sha Zhengju
2012-10-19 4:11 ` Sha Zhengju
[not found] ` <5080D308.1020805-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-10-19 9:52 ` Michal Hocko
2012-10-19 9:52 ` Michal Hocko
2012-10-19 9:52 ` Michal Hocko
[not found] ` <20121016133439.GI13991-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2012-10-16 18:39 ` David Rientjes
2012-10-16 18:39 ` David Rientjes
2012-10-16 18:39 ` David Rientjes
2012-10-16 18:44 ` David Rientjes
2012-10-16 18:44 ` David Rientjes
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:10 ` Sha Zhengju
2012-10-16 6:10 ` Sha Zhengju
[not found] ` <1350367837-27919-1-git-send-email-handai.szj-3b8fjiQLQpfQT0dZR+AlfA@public.gmane.org>
2012-10-16 6:12 ` David Rientjes
2012-10-16 6:12 ` David Rientjes
2012-10-16 6:12 ` David Rientjes
2012-10-16 6:32 ` Sha Zhengju
2012-10-16 6:32 ` Sha Zhengju
2012-10-16 7:03 ` Michal Hocko
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-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=handai.szj-3b8fjiQLQpfQT0dZR+AlfA@public.gmane.org \
--cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=nizhan.chen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.