Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753547Ab2F3Jtt (ORCPT ); Sat, 30 Jun 2012 05:49:49 -0400 Received: from na3sys010aog110.obsmtp.com ([74.125.245.88]:38414 "HELO na3sys010aog110.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752200Ab2F3Jts (ORCPT ); Sat, 30 Jun 2012 05:49:48 -0400 X-Greylist: delayed 377 seconds by postgrey-1.27 at vger.kernel.org; Sat, 30 Jun 2012 05:49:47 EDT Message-ID: <4FEECA3C.5070308@ravellosystems.com> Date: Sat, 30 Jun 2012 12:43:24 +0300 From: Izik Eidus User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: David Rientjes CC: Andrew Morton , Petr Holasek , Hugh Dickins , Andrea Arcangeli , Chris Wright , Rik van Riel , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Anton Arapov Subject: Re: [PATCH v2] KSM: numa awareness sysfs knob References: <1340970592-25001-1-git-send-email-pholasek@redhat.com> <20120629141759.3312b49e.akpm@linux-foundation.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1427 Lines: 39 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/