linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Jianguo Wu <wujianguo106@gmail.com>
Cc: akpm@linux-foundation.org, aarcange@redhat.com,
	kirill.shutemov@linux.intel.com, mgorman@suse.de,
	xiaoguangrong@linux.vnet.ibm.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, Jianguo Wu <wujianguo@huawei.com>
Subject: Re: [PATCH] mm/thp: fix comments in transparent_hugepage_flags
Date: Thu, 5 Sep 2013 10:11:45 +0800	[thread overview]
Message-ID: <20130905021144.GB27516@hacker.(null)> (raw)
In-Reply-To: <1378301422-9468-1-git-send-email-wujianguo@huawei.com>

Hi Jianguo,
On Wed, Sep 04, 2013 at 09:30:22PM +0800, Jianguo Wu wrote:
>Since commit d39d33c332(thp: enable direct defrag), defrag is enable
>for all transparent hugepage page faults by default, not only in
>MADV_HUGEPAGE regions.
>
>Signed-off-by: Jianguo Wu <wujianguo@huawei.com>
>---
> mm/huge_memory.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
>diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>index a92012a..abf047e 100644
>--- a/mm/huge_memory.c
>+++ b/mm/huge_memory.c
>@@ -28,10 +28,8 @@
>
> /*
>  * By default transparent hugepage support is enabled for all mappings

This is also stale. TRANSPARENT_HUGEPAGE_ALWAYS is not configured by default in
order that avoid to risk increase the memory footprint of applications w/o a 
guaranteed benefit.

Regards,
Wanpeng Li 

>- * and khugepaged scans all mappings. Defrag is only invoked by
>- * khugepaged hugepage allocations and by page faults inside
>- * MADV_HUGEPAGE regions to avoid the risk of slowing down short lived
>- * allocations.
>+ * and khugepaged scans all mappings. Defrag is invoked by khugepaged
>+ * hugepage allocations and by page faults for all hugepage allocations.
>  */
> unsigned long transparent_hugepage_flags __read_mostly =
> #ifdef CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS
>-- 
>1.8.1.2
>
>--
>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>

--
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>

  parent reply	other threads:[~2013-09-05  2:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 13:30 [PATCH] mm/thp: fix comments in transparent_hugepage_flags Jianguo Wu
2013-09-05  2:11 ` Wanpeng Li
2013-09-05  2:11 ` Wanpeng Li [this message]
     [not found] ` <5227e870.ab42320a.62d4.3d12SMTPIN_ADDED_BROKEN@mx.google.com>
2013-09-05  3:04   ` Jianguo Wu
2013-09-05  3:37     ` Wanpeng Li
2013-09-05  3:54       ` Jianguo Wu
2013-09-05  4:58         ` Wanpeng Li
2013-09-05  4:58         ` Wanpeng Li
     [not found]         ` <52280f92.e72b320a.2501.6de1SMTPIN_ADDED_BROKEN@mx.google.com>
2013-09-05  6:34           ` Jianguo Wu
2013-09-05  7:27             ` Wanpeng Li
2013-09-05  7:27             ` Wanpeng Li
2013-09-05  3:37     ` Wanpeng Li

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='20130905021144.GB27516@hacker.(null)' \
    --to=liwanp@linux.vnet.ibm.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=wujianguo106@gmail.com \
    --cc=wujianguo@huawei.com \
    --cc=xiaoguangrong@linux.vnet.ibm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).