From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx178.postini.com [74.125.245.178]) by kanga.kvack.org (Postfix) with SMTP id 0A2E56B0072 for ; Tue, 5 Jun 2012 03:47:19 -0400 (EDT) Received: by ggm4 with SMTP id 4so4849514ggm.14 for ; Tue, 05 Jun 2012 00:47:18 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4FCD14F1.1030105@gmail.com> References: <20120507121527.GA19526@lizard> <4FA82056.2070706@gmail.com> <20120601122118.GA6128@lizard> <4FCC7592.9030403@kernel.org> <20120604113811.GA4291@lizard> <4FCD14F1.1030105@gmail.com> Date: Tue, 5 Jun 2012 10:47:18 +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 Mon, Jun 4, 2012 at 11:05 PM, KOSAKI Motohiro wrote: >> Note that 1) and 2) are not problems per se, it's just implementation >> details, easy stuff. Vmevent is basically an ABI/API, and I didn't >> hear anybody who would object to vmevent ABI idea itself. More than >> this, nobody stop us from implementing in-kernel vmevent API, and >> make Android Lowmemory killer use it, if we want to. > > I never agree "it's mere ABI" discussion. Until the implementation is ugly, > I never agree the ABI even if syscall interface is very clean. I don't know what discussion you are talking about. I also don't agree that something should be merged just because the ABI is clean. The implementation must also make sense. I don't see how we disagree here at all. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org