Re: 答复: Too easy OOM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Li,Rongqing" <lirongqing@xxxxxxxxx>
Subject: Re: 答复: Too easy OOM
From: Michal Hocko <mhocko@xxxxxxxxxx>
Date: Wed, 28 Mar 2018 14:58:30 +0200
Cc: Austin Kim <austincrashtool@xxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <2AD939572F25A448A3AE3CAEA61328C237512B38@BC-MAIL-M28.internal.baidu.com>
References: <2AD939572F25A448A3AE3CAEA61328C23750D4E0@BC-MAIL-M28.internal.baidu.com> <CAKEcN828eqXN8zhKgzu+Mf-vdXC8o_LOmxwWZ4vayrdvmpdPFQ@mail.gmail.com> <2AD939572F25A448A3AE3CAEA61328C237512B38@BC-MAIL-M28.internal.baidu.com>
User-agent: Mutt/1.9.4 (2018-02-28)

On Wed 28-03-18 01:34:24, Li,Rongqing wrote:
> OK, I see this commit, I will test the latest kernel
> 
> commit 1c610d5f93c709df56787f50b3576704ac271826
> Author: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
> Date:   Thu Mar 22 16:17:42 2018 -0700

Yes, that should fix your memcg OOM
-- 
Michal Hocko
SUSE Labs

References:
- Too easy OOM
  - From: Li,Rongqing
- Re: Too easy OOM
  - From: Austin Kim
- 答复: Too easy OOM
  - From: Li,Rongqing

Prev by Date: Re: [PATCH] mm: Introduce i_mmap_lock_write_killable().
Next by Date: Re: [PATCH 2/2] smp: introduce kick_active_cpus_sync()
Previous by thread: 答复: Too easy OOM
Next by thread: [PATCH] mm: Introduce i_mmap_lock_write_killable().
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux