From: Sasha Levin <sasha.levin@oracle.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mel Gorman <mgorman@suse.de>, 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 15:12:55 -0400 [thread overview]
Message-ID: <542DA3B7.8090901@oracle.com> (raw)
In-Reply-To: <20141002190734.GA15671@node.dhcp.inet.fi>
On 10/02/2014 03:07 PM, Kirill A. Shutemov wrote:
> On Thu, Oct 02, 2014 at 12:03:58PM -0700, Linus Torvalds wrote:
>> > On Thu, Oct 2, 2014 at 11:58 AM, Sasha Levin <sasha.levin@oracle.com> wrote:
>>> > >
>>> > > 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.
>> >
>> > So not having a NUMA machine (and not really wanting one), I can't
>> > really test things like the migration even *working*.
> I believe Sasha uses fakenuma in his KVM for that.
That's true. You can impose arbitrary configurations on your kernel even without your
hardware telling you to...
Thanks,
Sasha
next prev parent reply other threads:[~2014-10-02 19:13 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
2014-10-02 19:03 ` Linus Torvalds
2014-10-02 19:07 ` Kirill A. Shutemov
2014-10-02 19:12 ` Sasha Levin [this message]
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=542DA3B7.8090901@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=kirill@shutemov.name \
--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.