linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Liang Chen <liangchen.linux@gmail.com>
Cc: "riel@redhat.com" <riel@redhat.com>,
	"mgorman@suse.de" <mgorman@suse.de>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Gavin Guo <gavin.guo@canonical.com>
Subject: Re: [PATCH V2] mm: mempolicy: skip non-migratable VMAs when setting MPOL_MF_LAZY
Date: Wed, 13 Jan 2016 08:16:12 +0000	[thread overview]
Message-ID: <20160113081611.GA29313@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <1452138758-30031-1-git-send-email-liangchen.linux@gmail.com>

Hello Liang,

On Thu, Jan 07, 2016 at 11:52:38AM +0800, Liang Chen wrote:
> MPOL_MF_LAZY is not visible from userspace since 'commit a720094ded8c
> ("mm: mempolicy: Hide MPOL_NOOP and MPOL_MF_LAZY from userspace for now")'
> , but it should still skip non-migratable VMAs such as VM_IO, VM_PFNMAP,
> and VM_HUGETLB VMAs, and avoid useless overhead of minor faults.
> 
> Signed-off-by: Liang Chen <liangchen.linux@gmail.com>
> Signed-off-by: Gavin Guo <gavin.guo@canonical.com>
> ---
> Changes since v2:
> - Add more description into the changelog
> 
> We have been evaluating the enablement of MPOL_MF_LAZY again, and found
> this issue. And we decided to push this patch upstream no matter if we
> finally determine to propose re-enablement of MPOL_MF_LAZY or not. Since
> it can be a potential problem even if MPOL_MF_LAZY is not enabled this
> time.
> ---
>  mm/mempolicy.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> index 87a1779..436ff411 100644
> --- a/mm/mempolicy.c
> +++ b/mm/mempolicy.c
> @@ -610,7 +610,8 @@ 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->vm_flags & (VM_READ | VM_EXEC | VM_WRITE))
> +		if (vma_migratable(vma) &&
> +			vma->vm_flags & (VM_READ | VM_EXEC | VM_WRITE))
>  			change_prot_numa(vma, start, endvma);
>  		return 1;
>  	}

task_numa_work() does more vma checks before entering change_prot_numa() like
vma_policy_mof(), is_vm_hugetlb_page(), and (vma->vm_flags & VM_MIXEDMAP).
So is it better to use the same check set to limit the target vmas to auto-numa
enabled ones?

Thanks,
Naoya Horiguchi
--
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-13  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07  3:52 Liang Chen
2016-01-13  8:16 ` Naoya Horiguchi [this message]
2016-01-15 12:54   ` Liang Chen

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=20160113081611.GA29313@hori1.linux.bs1.fc.nec.co.jp \
    --to=n-horiguchi@ah.jp.nec.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=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