[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOJsxLEeHR8MLAGteN_noU9Ncc+Q4eMVhQO7yDwxLQTTXrjJog@mail.gmail.com>
Date: Fri, 8 Jun 2012 09:57:09 +0300
From: Pekka Enberg <penberg@...nel.org>
To: KOSAKI Motohiro <kosaki.motohiro@...il.com>
Cc: Anton Vorontsov <cbouatmailru@...il.com>,
Minchan Kim <minchan@...nel.org>,
Leonid Moiseichuk <leonid.moiseichuk@...ia.com>,
John Stultz <john.stultz@...aro.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linaro-kernel@...ts.linaro.org,
patches@...aro.org, kernel-team@...roid.com
Subject: Re: [PATCH 0/5] Some vmevent fixes...
On Fri, Jun 8, 2012 at 6:45 AM, KOSAKI Motohiro
<kosaki.motohiro@...il.com> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists