[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <542DA767.3000601@redhat.com>
Date: Thu, 02 Oct 2014 15:28:39 -0400
From: Rik van Riel <riel@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
"Kirill A. Shutemov" <kirill@...temov.name>
CC: Sasha Levin <sasha.levin@...cle.com>, Mel Gorman <mgorman@...e.de>,
Dave Jones <davej@...hat.com>, Hugh Dickins <hughd@...gle.com>,
Al Viro <viro@...iv.linux.org.uk>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Aneesh Kumar <aneesh.kumar@...ux.vnet.ibm.com>,
Michel Lespinasse <walken@...gle.com>,
Kirill A Shutemov <kirill.shutemov@...ux.intel.com>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] mm: numa: Do not mark PTEs pte_numa when splitting
huge pages
On 10/02/2014 03:26 PM, Linus Torvalds wrote:
> On Thu, Oct 2, 2014 at 12:07 PM, Kirill A. Shutemov
> <kirill@...temov.name> wrote:
>>
>> I believe Sasha uses fakenuma in his KVM for that.
>
> Ok, so the benchmarks won't do anything then.
>
> I mean, I guess they might show some of the migration overhead, but
> they won't show the actual end result in any meaningful manner, since
> memory isn't actually NUMA.
Both autonuma and "perf bench numa mem" mostly tell us how
quickly the kernel manages to locate tasks and their memory
on the nodes where they belong, without doing much in the
way of NUMA performance measuring.
They are more useful as sanity tests than anything else.
"Does the kernel still properly place each process on its
own node, and how quickly does it do that?"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists