Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755119Ab2FHG5N (ORCPT ); Fri, 8 Jun 2012 02:57:13 -0400 Received: from mail-yw0-f46.google.com ([209.85.213.46]:48286 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752555Ab2FHG5L (ORCPT ); Fri, 8 Jun 2012 02:57:11 -0400 MIME-Version: 1.0 In-Reply-To: <4FD17564.9060209@gmail.com> References: <20120601122118.GA6128@lizard> <4FCC7592.9030403@kernel.org> <20120604113811.GA4291@lizard> <4FCD14F1.1030105@gmail.com> <20120604223951.GA20591@lizard> <4FD17564.9060209@gmail.com> Date: Fri, 8 Jun 2012 09:57:09 +0300 X-Google-Sender-Auth: pruK5gK_BEso5kMHD9yMJso2odI Message-ID: Subject: Re: [PATCH 0/5] Some vmevent fixes... From: Pekka Enberg To: KOSAKI Motohiro Cc: Anton Vorontsov , Minchan Kim , Leonid Moiseichuk , John Stultz , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org, patches@linaro.org, kernel-team@android.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 755 Lines: 15 On Fri, Jun 8, 2012 at 6:45 AM, KOSAKI Motohiro wrote: > So, big design choice here. 1) vmevent is a just notification. it can't > guarantee to prevent oom. or 2) to implement some trick (e.g. reserved > memory for vmevent processes, kernel activity blocking until finish > memory returing, etc) Yes, vmevent is only for notification and will not *guarantee* OOM prevention. It simply tries to provide hints early enough to the userspace to so that OOM can be avoided if possible. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/