From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx189.postini.com [74.125.245.189]) by kanga.kvack.org (Postfix) with SMTP id 63E3D6B006E for ; Fri, 8 Jun 2012 02:57:11 -0400 (EDT) Received: by yhr47 with SMTP id 47so1379443yhr.14 for ; Thu, 07 Jun 2012 23:57:10 -0700 (PDT) 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 Message-ID: Subject: Re: [PATCH 0/5] Some vmevent fixes... From: Pekka Enberg Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: 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 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, 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: email@kvack.org