linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Mel Gorman <mgorman@suse.de>
Cc: Dave Jones <davej@redhat.com>, 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, 02 Oct 2014 14:58:00 -0400	[thread overview]
Message-ID: <542DA038.9000908@oracle.com> (raw)
In-Reply-To: <CA+55aFzJtoEXEzoyYQ=j+AMxyZNL3Gr3bhXPr3twyuGzvES1PA@mail.gmail.com>

On 10/02/2014 12:36 PM, Linus Torvalds wrote:
> On Thu, Oct 2, 2014 at 6:29 AM, Mel Gorman <mgorman@suse.de> 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.
> So this is the particular bug I was worried about when tracing through the code.
> 
> Should I just apply this as-is? And mark it for stable, since this has
> been around since 3.8 or so. It would seem to be a very safe change to
> do, regardless of whether this is actually the issue that Dave and
> maybe Sasha are seeing.
> 
> Sasha, I notice that you weren't on the cc for Mel's patches (probably
> because you got added later to the other thread), but they were all
> cc'd to lkml so you should see them there. Or I can forward them
> separately.

I grabbed them and will keep them in my tree for now instead of your
NUMA-chainsaw-massacre patch.

You've also mentioned that while I can tell you if nothing dies, I can't
really tell you if everything is working well. Is there a reasonable way
to easily say if NUMA is working properly? Even something that would just
tell me "your NUMA balancing seems to be sane" would be good.


Thanks,
Sasha

  reply	other threads:[~2014-10-02 18:58 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
2014-10-02 16:19   ` Rik van Riel
2014-10-02 16:36   ` Linus Torvalds
2014-10-02 18:58     ` Sasha Levin [this message]
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=542DA038.9000908@oracle.com \
    --to=sasha.levin@oracle.com \
    --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 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).