All of lore.kernel.org
 help / color / mirror / Atom feed
From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-kernel@vger.kernel.org, Dave Hansen <dave.hansen@intel.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Mel Gorman <mgorman@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org
Subject: Re: [RFC] mm: show message when updating min_free_kbytes in thp
Date: Wed, 8 Jan 2014 11:59:46 +0800	[thread overview]
Message-ID: <20140108035946.GI4106@localhost.localdomain> (raw)
In-Reply-To: <20140106164604.GC27602@dhcp22.suse.cz>

On Mon, Jan 06, 2014 at 05:46:04PM +0100, Michal Hocko wrote:
> On Sun 05-01-14 08:35:01, Han Pingtian wrote:
> [...]
> > From f4d085a880dfae7638b33c242554efb0afc0852b Mon Sep 17 00:00:00 2001
> > From: Han Pingtian <hanpt@linux.vnet.ibm.com>
> > Date: Fri, 3 Jan 2014 11:10:49 +0800
> > Subject: [PATCH] mm: show message when raising min_free_kbytes in THP
> > 
> > min_free_kbytes may be raised during THP's initialization. Sometimes,
> > this will change the value being set by user. Showing message will
> > clarify this confusion.
> 
> I do not have anything against informing about changing value
> set by user but this will inform also when the default value is
> updated. Is this what you want? Don't you want to check against
> user_min_free_kbytes? (0 if not set by user)
> 
But looks like the user can set min_free_kbytes to 0 by

    echo 0 > /proc/sys/vm/min_free_kbytes

and even set it to -1 the same way. So I think we need to restrict the
value of min_free_kbytes > 0 first?

> Btw. Do we want to restore the original value when khugepaged is
> disabled?
> 

--
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: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-kernel@vger.kernel.org, Dave Hansen <dave.hansen@intel.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Mel Gorman <mgorman@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org
Subject: Re: [RFC] mm: show message when updating min_free_kbytes in thp
Date: Wed, 8 Jan 2014 11:59:46 +0800	[thread overview]
Message-ID: <20140108035946.GI4106@localhost.localdomain> (raw)
In-Reply-To: <20140106164604.GC27602@dhcp22.suse.cz>

On Mon, Jan 06, 2014 at 05:46:04PM +0100, Michal Hocko wrote:
> On Sun 05-01-14 08:35:01, Han Pingtian wrote:
> [...]
> > From f4d085a880dfae7638b33c242554efb0afc0852b Mon Sep 17 00:00:00 2001
> > From: Han Pingtian <hanpt@linux.vnet.ibm.com>
> > Date: Fri, 3 Jan 2014 11:10:49 +0800
> > Subject: [PATCH] mm: show message when raising min_free_kbytes in THP
> > 
> > min_free_kbytes may be raised during THP's initialization. Sometimes,
> > this will change the value being set by user. Showing message will
> > clarify this confusion.
> 
> I do not have anything against informing about changing value
> set by user but this will inform also when the default value is
> updated. Is this what you want? Don't you want to check against
> user_min_free_kbytes? (0 if not set by user)
> 
But looks like the user can set min_free_kbytes to 0 by

    echo 0 > /proc/sys/vm/min_free_kbytes

and even set it to -1 the same way. So I think we need to restrict the
value of min_free_kbytes > 0 first?

> Btw. Do we want to restore the original value when khugepaged is
> disabled?
> 


  reply	other threads:[~2014-01-08  3:59 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01  0:29 [RFC] mm: show message when updating min_free_kbytes in thp Han Pingtian
2014-01-01  0:29 ` Han Pingtian
2014-01-02 18:05 ` Dave Hansen
2014-01-02 18:05   ` Dave Hansen
2014-01-02 21:58   ` David Rientjes
2014-01-02 21:58     ` David Rientjes
2014-01-02 22:10     ` Dave Hansen
2014-01-02 22:10       ` Dave Hansen
2014-01-02 23:36       ` David Rientjes
2014-01-02 23:36         ` David Rientjes
2014-01-02 23:48         ` Dave Hansen
2014-01-02 23:48           ` Dave Hansen
2014-01-03  3:33   ` Han Pingtian
2014-01-03  3:33     ` Han Pingtian
2014-01-03 18:17     ` Dave Hansen
2014-01-03 18:17       ` Dave Hansen
2014-01-05  0:35       ` Han Pingtian
2014-01-05  0:35         ` Han Pingtian
2014-01-06 16:46         ` Michal Hocko
2014-01-06 16:46           ` Michal Hocko
2014-01-08  3:59           ` Han Pingtian [this message]
2014-01-08  3:59             ` Han Pingtian
2014-01-08  8:20           ` Han Pingtian
2014-01-08  8:20             ` Han Pingtian
2014-01-08 10:16             ` Michal Hocko
2014-01-08 10:16               ` Michal Hocko
2014-01-09  7:32               ` Han Pingtian
2014-01-09  7:32                 ` Han Pingtian
2014-01-09  9:02                 ` Michal Hocko
2014-01-09  9:02                   ` Michal Hocko
2014-01-09 21:15                 ` David Rientjes
2014-01-09 21:15                   ` David Rientjes
2014-01-10  8:05                   ` Michal Hocko
2014-01-10  8:05                     ` Michal Hocko
2014-01-10  8:13                     ` Andrew Morton
2014-01-10  8:13                       ` Andrew Morton
2014-01-10  8:17                       ` Michal Hocko
2014-01-10  8:17                         ` Michal Hocko
2014-01-11  3:27                         ` Han Pingtian
2014-01-11  3:27                           ` Han Pingtian
2014-01-14 20:07                         ` Han Pingtian
2014-01-14 20:07                           ` Han Pingtian
2014-01-14 23:52                           ` Andrew Morton
2014-01-14 23:52                             ` Andrew Morton
2014-01-15  0:25                             ` David Rientjes
2014-01-15  0:25                               ` David Rientjes
2014-01-15  0:35                               ` Andrew Morton
2014-01-15  0:35                                 ` Andrew Morton
2014-01-15  0:52                                 ` David Rientjes
2014-01-15  0:52                                   ` David Rientjes
2014-01-15 15:22                                 ` Mel Gorman
2014-01-15 15:22                                   ` Mel Gorman

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=20140108035946.GI4106@localhost.localdomain \
    --to=hanpt@linux.vnet.ibm.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.cz \
    /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.