From: Izik Eidus <izik.eidus@ravellosystems.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Petr Holasek <pholasek@redhat.com>,
Hugh Dickins <hughd@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Chris Wright <chrisw@sous-sol.org>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Anton Arapov <anton@redhat.com>
Subject: Re: [PATCH v2] KSM: numa awareness sysfs knob
Date: Sat, 30 Jun 2012 12:43:24 +0300 [thread overview]
Message-ID: <4FEECA3C.5070308@ravellosystems.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206291543360.17044@chino.kir.corp.google.com>
On 06/30/2012 01:50 AM, David Rientjes wrote:
> On Fri, 29 Jun 2012, Andrew Morton wrote:
>
>>> I've tested this patch on numa machines with 2, 4 and 8 nodes and
>>> measured speed of memory access inside of KVM guests with memory pinned
>>> to one of nodes with this benchmark:
>>>
>>> http://pholasek.fedorapeople.org/alloc_pg.c
>>>
>>> Population standard deviations of access times in percentage of average
>>> were following:
>>>
>>> merge_nodes=1
>>> 2 nodes 1.4%
>>> 4 nodes 1.6%
>>> 8 nodes 1.7%
>>>
>>> merge_nodes=0
>>> 2 nodes 1%
>>> 4 nodes 0.32%
>>> 8 nodes 0.018%
>> ooh, numbers! Thanks.
>>
> Ok, the standard deviation increases when merging pages from nodes with
> remote distance, that makes sense. But if that's true, then you would
> restrict either the entire application to local memory with mempolicies or
> cpusets, or you would use mbind() to restrict this memory to that set of
> nodes already so that accesses, even with ksm merging, would have
> affinity.
While you are right for case you write your own custom application,
but I think the KVM guest case is little bit more problomatic in case
the guest memory must be splitted across serval nodes.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Izik Eidus <izik.eidus@ravellosystems.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Petr Holasek <pholasek@redhat.com>,
Hugh Dickins <hughd@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Chris Wright <chrisw@sous-sol.org>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Anton Arapov <anton@redhat.com>
Subject: Re: [PATCH v2] KSM: numa awareness sysfs knob
Date: Sat, 30 Jun 2012 12:43:24 +0300 [thread overview]
Message-ID: <4FEECA3C.5070308@ravellosystems.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206291543360.17044@chino.kir.corp.google.com>
On 06/30/2012 01:50 AM, David Rientjes wrote:
> On Fri, 29 Jun 2012, Andrew Morton wrote:
>
>>> I've tested this patch on numa machines with 2, 4 and 8 nodes and
>>> measured speed of memory access inside of KVM guests with memory pinned
>>> to one of nodes with this benchmark:
>>>
>>> http://pholasek.fedorapeople.org/alloc_pg.c
>>>
>>> Population standard deviations of access times in percentage of average
>>> were following:
>>>
>>> merge_nodes=1
>>> 2 nodes 1.4%
>>> 4 nodes 1.6%
>>> 8 nodes 1.7%
>>>
>>> merge_nodes=0
>>> 2 nodes 1%
>>> 4 nodes 0.32%
>>> 8 nodes 0.018%
>> ooh, numbers! Thanks.
>>
> Ok, the standard deviation increases when merging pages from nodes with
> remote distance, that makes sense. But if that's true, then you would
> restrict either the entire application to local memory with mempolicies or
> cpusets, or you would use mbind() to restrict this memory to that set of
> nodes already so that accesses, even with ksm merging, would have
> affinity.
While you are right for case you write your own custom application,
but I think the KVM guest case is little bit more problomatic in case
the guest memory must be splitted across serval nodes.
next prev parent reply other threads:[~2012-06-30 9:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 11:49 [PATCH v2] KSM: numa awareness sysfs knob Petr Holasek
2012-06-29 11:49 ` Petr Holasek
2012-06-29 13:03 ` Cong Wang
2012-06-29 13:23 ` Petr Holasek
2012-06-29 13:23 ` Petr Holasek
2012-06-29 16:05 ` Johannes Weiner
2012-06-29 16:05 ` Johannes Weiner
2012-06-29 16:30 ` Petr Holasek
2012-06-29 16:30 ` Petr Holasek
2012-06-29 16:47 ` Johannes Weiner
2012-06-29 16:47 ` Johannes Weiner
2012-06-29 22:30 ` David Rientjes
2012-06-29 22:30 ` David Rientjes
2012-06-30 11:40 ` Petr Holasek
2012-06-30 11:40 ` Petr Holasek
2012-07-02 21:26 ` David Rientjes
2012-07-02 21:26 ` David Rientjes
2012-07-03 17:02 ` Petr Holasek
2012-07-03 17:02 ` Petr Holasek
2012-06-29 21:17 ` Andrew Morton
2012-06-29 21:17 ` Andrew Morton
2012-06-29 22:50 ` David Rientjes
2012-06-29 22:50 ` David Rientjes
2012-06-30 9:43 ` Izik Eidus [this message]
2012-06-30 9:43 ` Izik Eidus
2012-06-30 12:29 ` Petr Holasek
2012-06-30 12:29 ` Petr Holasek
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=4FEECA3C.5070308@ravellosystems.com \
--to=izik.eidus@ravellosystems.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anton@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pholasek@redhat.com \
--cc=riel@redhat.com \
--cc=rientjes@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.