From: Andrew Morton <akpm@linux-foundation.org>
To: Fengwei Yin <yfw.kernel@gmail.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCH v2] smaps should deal with huge zero page exactly same as normal zero page.
Date: Mon, 27 Oct 2014 15:17:48 -0700	[thread overview]
Message-ID: <20141027151748.3901b18abcb65426e7ed50b0@linux-foundation.org> (raw)
In-Reply-To: <1414422133-7929-1-git-send-email-yfw.kernel@gmail.com>
On Mon, 27 Oct 2014 23:02:13 +0800 Fengwei Yin <yfw.kernel@gmail.com> wrote:
> We could see following memory info in /proc/xxxx/smaps with THP enabled.
>   7bea458b3000-7fea458b3000 r--p 00000000 00:13 39989  /dev/zero
>   Size:           4294967296 kB
>   Rss:            10612736 kB
>   Pss:            10612736 kB
>   Shared_Clean:          0 kB
>   Shared_Dirty:          0 kB
>   Private_Clean:  10612736 kB
>   Private_Dirty:         0 kB
>   Referenced:     10612736 kB
>   Anonymous:             0 kB
>   AnonHugePages:  10612736 kB
>   Swap:                  0 kB
>   KernelPageSize:        4 kB
>   MMUPageSize:           4 kB
>   Locked:                0 kB
>   VmFlags: rd mr mw me
> which is wrong becuase just huge_zero_page/normal_zero_page is used for
> /dev/zero. Most of the value should be 0.
> 
> This patch detects huge_zero_page (original implementation just detect
> normal_zero_page) and avoids to update the wrong value for huge_zero_page.
> 
> ...
>
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -41,6 +41,7 @@
>  #include <linux/kernel_stat.h>
>  #include <linux/mm.h>
>  #include <linux/hugetlb.h>
> +#include <linux/huge_mm.h>
>  #include <linux/mman.h>
>  #include <linux/swap.h>
>  #include <linux/highmem.h>
> @@ -787,6 +788,9 @@ check_pfn:
>  		return NULL;
>  	}
>  
> +	if (is_huge_zero_pfn(pfn))
> +		return NULL;
> +
Why this change?
What effect does it have upon vm_normal_page()'s many existing callers?
--
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>
next prev parent reply	other threads:[~2014-10-27 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 15:02 [PATCH v2] smaps should deal with huge zero page exactly same as normal zero page Fengwei Yin
2014-10-27 22:17 ` Andrew Morton [this message]
2014-10-28 15:18   ` Fengwei Yin
2014-10-28 13:18     ` Kirill A. Shutemov
2014-10-29 16:54       ` Fengwei Yin
2014-10-28 15:44   ` Fengwei Yin
2014-10-28 20:35     ` Andrew Morton
2014-10-28 20:40       ` Andrew Morton
2014-10-30 14:04         ` Fengwei Yin
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=20141027151748.3901b18abcb65426e7ed50b0@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=kirill@shutemov.name \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=yfw.kernel@gmail.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).