All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <anton@enomsg.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org, mhocko@suse.cz,
	akpm@linux-foundation.org
Subject: Re: [PATCH] vmpressure: implement strict mode
Date: Wed, 26 Jun 2013 11:00:43 -0700	[thread overview]
Message-ID: <20130626180042.GA9827@teo> (raw)
In-Reply-To: <20130626075051.GG29127@bbox>

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 <lcapitulino@redhat.com>
> Acked-by: Minchan Kim <minchan@kernel.org>
> 
> 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, 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Anton Vorontsov <anton@enomsg.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org, mhocko@suse.cz,
	akpm@linux-foundation.org
Subject: Re: [PATCH] vmpressure: implement strict mode
Date: Wed, 26 Jun 2013 11:00:43 -0700	[thread overview]
Message-ID: <20130626180042.GA9827@teo> (raw)
In-Reply-To: <20130626075051.GG29127@bbox>

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 <lcapitulino@redhat.com>
> Acked-by: Minchan Kim <minchan@kernel.org>
> 
> 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

  parent reply	other threads:[~2013-06-26 18:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 21:51 [PATCH] vmpressure: implement strict mode Luiz Capitulino
2013-06-25 21:51 ` Luiz Capitulino
2013-06-26  0:28 ` Kyungmin Park
2013-06-26  0:28   ` Kyungmin Park
2013-06-26  1:12   ` Hyunhee Kim
2013-06-26  1:12     ` Hyunhee Kim
2013-06-26  3:20     ` Luiz Capitulino
2013-06-26  3:20       ` Luiz Capitulino
2013-06-26  4:03 ` Anton Vorontsov
2013-06-26  4:03   ` Anton Vorontsov
2013-06-26 13:32   ` Luiz Capitulino
2013-06-26 13:32     ` Luiz Capitulino
2013-06-26  7:50 ` Minchan Kim
2013-06-26  7:50   ` Minchan Kim
2013-06-26  7:59   ` Michal Hocko
2013-06-26  7:59     ` Michal Hocko
2013-06-26  8:20     ` Minchan Kim
2013-06-26  8:20       ` Minchan Kim
2013-06-26 13:44       ` Luiz Capitulino
2013-06-26 13:44         ` Luiz Capitulino
2013-06-26 18:00   ` Anton Vorontsov [this message]
2013-06-26 18:00     ` Anton Vorontsov
2013-06-26  8:08 ` Michal Hocko
2013-06-26  8:08   ` Michal Hocko
2013-06-26 13:45   ` Luiz Capitulino
2013-06-26 13:45     ` Luiz Capitulino
2013-07-01  8:51 ` Pavel Machek
2013-07-01  8:51   ` Pavel Machek
2013-07-02 15:06   ` Luiz Capitulino
2013-07-02 15:06     ` Luiz Capitulino
2013-07-02 19:47     ` Pavel Machek
2013-07-02 19:47       ` Pavel Machek
2013-07-02 21:55       ` Luiz Capitulino
2013-07-02 21:55         ` Luiz Capitulino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130626180042.GA9827@teo \
    --to=anton@enomsg.org \
    --cc=akpm@linux-foundation.org \
    --cc=lcapitulino@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=minchan@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.