Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1578329

Re: [RFC] 3.10 kernel- oom with about 24G free memory

From Yisheng Xie <xieyisheng1@huawei.com>
Newsgroups linux.kernel
Subject Re: [RFC] 3.10 kernel- oom with about 24G free memory
Date 2017-02-10 10:30 +0100
Message-ID <t9fGF-1x8-3@gated-at.bofh.it> (permalink)
References (2 earlier) <t8XgK-6Nm-5@gated-at.bofh.it> <t982u-5bz-7@gated-at.bofh.it> <t9dvc-fW-27@gated-at.bofh.it> <t9fdE-17p-17@gated-at.bofh.it> <t9fdE-17p-15@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Michal,

Thanks for comment!
On 2017/2/10 16:52, Michal Hocko wrote:
> On Fri 10-02-17 16:48:58, Yisheng Xie wrote:
>> Hi Michal,
>>
>> Thanks for comment!
>> On 2017/2/10 15:09, Michal Hocko wrote:
>>> On Fri 10-02-17 09:13:58, Yisheng Xie wrote:
>>>> hi Michal,
>>>> Thanks for your comment.
>>>>
>>>> On 2017/2/9 21:41, Michal Hocko wrote:
> [...]
>>>>>> OK, so this is a memcg OOM killer which panics because the configuration
>>>>>> says so. The OOM report doesn't say so and that is the bug. dump_header
>>>>>> is memcg aware and mem_cgroup_out_of_memory initializes oom_control
>>>>>> properly. Is this Vanilla kernel?
>>>>
>>>> That means we should raise the limit of that memcg to avoid memcg OOM killer, right?
>>>
>>> Why do you configure the system to panic on memcg OOM in the first
>>> place. This is a wrong thing to do in 99% of cases.
>>
>> For our production think it should use reboot to recovery the system when OOM,
>> instead of killing user's key process. Maybe not the right thing.
> 
> I can understand that for the global oom killer but not for memcg. You
> can recover the oom even without killing any process. You can simply
> increase the limit from the userspace when the oom event is triggered.
So you mean set oom_kill_disable and increase the limit from userspace
when memcg under_oom, right?

Thanks
Yisheng Xie.
> 
> Trigerring the panic on memcg oom killer is both dangerous and most
> probably something you do not want.
> 

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[RFC] 3.10 kernel- oom with about 24G free memory Yisheng Xie <xieyisheng1@huawei.com> - 2017-02-09 14:00 +0100
  Re: [RFC] 3.10 kernel- oom with about 24G free memory Michal Hocko <mhocko@kernel.org> - 2017-02-09 14:50 +0100
    Re: [RFC] 3.10 kernel- oom with about 24G free memory Yisheng Xie <xieyisheng1@huawei.com> - 2017-02-10 02:20 +0100
      Re: [RFC] 3.10 kernel- oom with about 24G free memory Michal Hocko <mhocko@kernel.org> - 2017-02-10 08:10 +0100
        Re: [RFC] 3.10 kernel- oom with about 24G free memory Michal Hocko <mhocko@kernel.org> - 2017-02-10 10:00 +0100
          Re: [RFC] 3.10 kernel- oom with about 24G free memory Michal Hocko <mhocko@kernel.org> - 2017-02-10 10:30 +0100
          Re: [RFC] 3.10 kernel- oom with about 24G free memory Yisheng Xie <xieyisheng1@huawei.com> - 2017-02-10 10:30 +0100
        Re: [RFC] 3.10 kernel- oom with about 24G free memory Yisheng Xie <xieyisheng1@huawei.com> - 2017-02-10 10:00 +0100
  Re: [RFC] 3.10 kernel- oom with about 24G free memory Michal Hocko <mhocko@kernel.org> - 2017-02-09 15:20 +0100
    Re: [RFC] 3.10 kernel- oom with about 24G free memory Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> - 2017-02-09 15:30 +0100

csiph-web