From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754284AbcALVAj (ORCPT ); Tue, 12 Jan 2016 16:00:39 -0500 Received: from mail-wm0-f49.google.com ([74.125.82.49]:35977 "EHLO mail-wm0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754249AbcALVAg (ORCPT ); Tue, 12 Jan 2016 16:00:36 -0500 From: Michal Hocko To: Cc: Tetsuo Handa , David Rientjes , LKML Subject: [RFC 0/3] oom: few enahancements Date: Tue, 12 Jan 2016 22:00:22 +0100 Message-Id: <1452632425-20191-1-git-send-email-mhocko@kernel.org> X-Mailer: git-send-email 2.6.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, based on the recent discussions I have accumulated the following three patches. I haven't tested them yet but I would like to hear your opinion. The first patch only affects sysrq+f OOM killer. I believe it should be relatively uncontroversial. The patch 2 tweaks how we handle children tasks standing for the parent oom victim. This should help the test case Tetsuo shown [1]. The patch 3 is just a rough idea. I can see objections there but this is mainly to start discussion about ho to deal with small children which basically do not sit on any memory. Maybe we do not need anything like that at all and realy on multiple OOM invocations as a safer option. I dunno but I would like to hear your opinions. --- [1] http://lkml.kernel.org/r/201512292258.ABF87505.OFOSJLHMFVOQFt%40I-love.SAKURA.ne.jp