linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj38.park@gmail.com>
To: Liang Chen <liangchen.linux@gmail.com>
Cc: n-horiguchi@ah.jp.nec.com, linux-mm@kvack.org, riel@redhat.com,
	mgorman@suse.de, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, Gavin Guo <gavin.guo@canonical.com>
Subject: Re: [PATCH] mm:mempolicy: skip VM_HUGETLB and VM_MIXEDMAP VMA for lazy mbind
Date: Tue, 19 Jan 2016 10:12:57 +0900 (KST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1601191005350.2469@hxeon> (raw)
In-Reply-To: <1453125834-16546-1-git-send-email-liangchen.linux@gmail.com>

Hello Liang,

Just trivial comment below.

On Mon, 18 Jan 2016, Liang Chen wrote:

> VM_HUGETLB and VM_MIXEDMAP vma needs to be excluded to avoid compound
> pages being marked for migration and unexpected COWs when handling
> hugetlb fault.
>
> Thanks to Naoya Horiguchi for reminding me on these checks.
>
> Signed-off-by: Liang Chen <liangchen.linux@gmail.com>
> Signed-off-by: Gavin Guo <gavin.guo@canonical.com>
> ---
> mm/mempolicy.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> index 436ff411..415de70 100644
> --- a/mm/mempolicy.c
> +++ b/mm/mempolicy.c
> @@ -610,8 +610,9 @@ static int queue_pages_test_walk(unsigned long start, unsigned long end,
>
> 	if (flags & MPOL_MF_LAZY) {
> 		/* Similar to task_numa_work, skip inaccessible VMAs */
> -		if (vma_migratable(vma) &&
> -			vma->vm_flags & (VM_READ | VM_EXEC | VM_WRITE))
> +		if (vma_migratable(vma) && !is_vm_hugetlb_page(vma) &&
> +			(vma->vm_flags & (VM_READ | VM_EXEC | VM_WRITE)) &&
> +			!(vma->vm_flags & VM_MIXEDMAP))

Isn't there exists few unnecessary parenthesis? IMHO, it makes me hard to 
read the code.

How about below code, instead?

+             if (vma_migratable(vma) && !is_vm_hugetlb_page(vma) &&
+                     vma->vm_flags & (VM_READ | VM_EXEC | VM_WRITE) &&
+                     !vma->vm_flags & VM_MIXEDMAP)


Thanks,
SeongJae Park.

> 			change_prot_numa(vma, start, endvma);
> 		return 1;
> 	}
> -- 
> 1.9.1
>
> --
> 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>

  reply	other threads:[~2016-01-19  1:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 14:03 Liang Chen
2016-01-19  1:12 ` SeongJae Park [this message]
2016-01-19  2:43   ` Gavin Guo
2016-01-19  3:00     ` SeongJae Park
2016-01-20 13:44       ` Liang Chen
2016-01-19 22:24 ` David Rientjes
2016-01-20 14:07   ` [PATCH v2] " Liang Chen
2016-01-20 23:32     ` David Rientjes

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=alpine.DEB.2.10.1601191005350.2469@hxeon \
    --to=sj38.park@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gavin.guo@canonical.com \
    --cc=liangchen.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=riel@redhat.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