All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Mel Gorman <mgorman@suse.de>
Cc: Dave Jones <davej@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Hugh Dickins <hughd@google.com>,
	Al Viro <viro@zeniv.linux.org.uk>, Rik van Riel <riel@redhat.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Aneesh Kumar <aneesh.kumar@linux.vnet.ibm.com>,
	Michel Lespinasse <walken@google.com>,
	Kirill A Shutemov <kirill.shutemov@linux.intel.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] mm: numa: Do not mark PTEs pte_numa when splitting huge pages
Date: Thu, 2 Oct 2014 18:18:07 +0300	[thread overview]
Message-ID: <20141002151807.GA13668@node.dhcp.inet.fi> (raw)
In-Reply-To: <1412256558-9995-5-git-send-email-mgorman@suse.de>

On Thu, Oct 02, 2014 at 02:29:18PM +0100, Mel Gorman wrote:
> This patch reverts 1ba6e0b50b ("mm: numa: split_huge_page: transfer the
> NUMA type from the pmd to the pte"). If a huge page is being split due
> a protection change and the tail will be in a PROT_NONE vma then NUMA
> hinting PTEs are temporarily created in the protected VMA.
> 
>  VM_RW|VM_PROTNONE
> |-----------------|
>       ^
>       split here
> 
> In the specific case above, it should get fixed up by change_pte_range()
> but there is a window of opportunity for weirdness to happen. Similarly,
> if a huge page is shrunk and split during a protection update but before
> pmd_numa is cleared then a pte_numa can be left behind.
> 
> Instead of adding complexity trying to deal with the case, this patch
> will not mark PTEs NUMA when splitting a huge page. NUMA hinting faults
> will not be triggered which is marginal in comparison to the complexity
> in dealing with the corner cases during THP split.
> 
> Signed-off-by: Mel Gorman <mgorman@suse.de>

I think it deserves a comment to avoid re-introducing NUMA type
transferring.

Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>

-- 
 Kirill A. Shutemov

  reply	other threads:[~2014-10-02 15:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 13:29 [PATCH 0/4] NUMA balancing related fixlets Mel Gorman
2014-10-02 13:29 ` [PATCH 1/4] mm: remove misleading ARCH_USES_NUMA_PROT_NONE (from Andrew's tree) Mel Gorman
2014-10-02 13:29 ` [PATCH 2/4] mm: migrate: Close race between migration completion and mprotect Mel Gorman
2014-10-02 15:48   ` Rik van Riel
2014-10-02 16:41   ` Linus Torvalds
2014-10-02 13:29 ` [PATCH 3/4] mm: mempolicy: Skip inaccessible VMAs when setting MPOL_MF_LAZY Mel Gorman
2014-10-02 15:51   ` Rik van Riel
2014-10-02 13:29 ` [PATCH 4/4] mm: numa: Do not mark PTEs pte_numa when splitting huge pages Mel Gorman
2014-10-02 15:18   ` Kirill A. Shutemov [this message]
2014-10-02 16:19   ` Rik van Riel
2014-10-02 16:36   ` Linus Torvalds
2014-10-02 18:58     ` Sasha Levin
2014-10-02 19:03       ` Linus Torvalds
2014-10-02 19:07         ` Kirill A. Shutemov
2014-10-02 19:12           ` Sasha Levin
2014-10-02 19:26           ` Linus Torvalds
2014-10-02 19:28             ` Rik van Riel
2014-10-02 19:32               ` Linus Torvalds

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=20141002151807.GA13668@node.dhcp.inet.fi \
    --to=kirill@shutemov.name \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=davej@redhat.com \
    --cc=hughd@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=walken@google.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 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.