Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752870Ab3FZSAs (ORCPT ); Wed, 26 Jun 2013 14:00:48 -0400 Received: from mail-pb0-f42.google.com ([209.85.160.42]:43665 "EHLO mail-pb0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752533Ab3FZSAq (ORCPT ); Wed, 26 Jun 2013 14:00:46 -0400 Date: Wed, 26 Jun 2013 11:00:43 -0700 From: Anton Vorontsov To: Minchan Kim Cc: Luiz Capitulino , linux-mm@kvack.org, linux-kernel@vger.kernel.org, mhocko@suse.cz, akpm@linux-foundation.org Subject: Re: [PATCH] vmpressure: implement strict mode Message-ID: <20130626180042.GA9827@teo> References: <20130625175129.7c0d79e1@redhat.com> <20130626075051.GG29127@bbox> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20130626075051.GG29127@bbox> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1470 Lines: 34 On Wed, Jun 26, 2013 at 04:50:51PM +0900, Minchan Kim wrote: > On Tue, Jun 25, 2013 at 05:51:29PM -0400, Luiz Capitulino wrote: > > Currently, applications are notified for the level they registered for > > _plus_ higher levels. > > > > This is a problem if the application wants to implement different > > actions for different levels. For example, an application might want > > to release 10% of its cache on level low, 50% on medium and 100% on > > critical. To do this, the application has to register a different fd > > for each event. However, fd low is always going to be notified and > > and all fds are going to be notified on level critical. > > > > Strict mode solves this problem by strictly notifiying the event > > an fd has registered for. It's optional. By default we still notify > > on higher levels. > > > > Signed-off-by: Luiz Capitulino > Acked-by: Minchan Kim > > Shouldn't we make this default? > What do you think about it? Either way works and both modes have their use-cases (as I have described in my previous mail). Changing the default mode is just unneeded churn, IMO. As long as things are documented properly, we are good. :) Thanks, Anton -- 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/