From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx177.postini.com [74.125.245.177]) by kanga.kvack.org (Postfix) with SMTP id DEF6F6B006E for ; Fri, 8 Jun 2012 02:54:16 -0400 (EDT) Received: by ggm4 with SMTP id 4so1364209ggm.14 for ; Thu, 07 Jun 2012 23:54:16 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4FD177BD.1070004@gmail.com> References: <20120507121527.GA19526@lizard> <4FA82056.2070706@gmail.com> <20120601122118.GA6128@lizard> <4FCC7592.9030403@kernel.org> <20120604113811.GA4291@lizard> <4FCD14F1.1030105@gmail.com> <4FD177BD.1070004@gmail.com> Date: Fri, 8 Jun 2012 09:54:15 +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:55 AM, KOSAKI Motohiro wrote: >> For some cases, yes, but probably not for all. >> >> For example, if userspace doesn't know about "about to swap real soon" >> condition, it can continue to grow its caches making >> fallocate(VOLATILE) pretty much useless. > > Fair enough. But, Please consider your scenario don't need vmevent(2), > cat /proc/meminfo works enough. Only dropping activity need a quick work > and just in time notification. cache growing limitation don't need. Why do you keep bringing this up? Yes, you might get away with polling /proc/meminfo or /proc/vmstat for some specific cases. It does not make it a proper generic solution to the problem "vmevent" ABI tries to address. -- 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