From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXByX-0005Xl-Ag for ltp-list@lists.sourceforge.net; Mon, 07 Apr 2014 16:00:45 +0000 Received: from qmta11.emeryville.ca.mail.comcast.net ([76.96.27.211]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1WXByV-0000lw-F4 for ltp-list@lists.sourceforge.net; Mon, 07 Apr 2014 16:00:45 +0000 Date: Mon, 7 Apr 2014 10:47:05 -0500 (CDT) From: Christoph Lameter In-Reply-To: <20140407013932.GU22728@two.firstfloor.org> Message-ID: References: <533D3BC7.8010309@oracle.com> <20140407013932.GU22728@two.firstfloor.org> Subject: Re: [LTP] numastats updates List-Id: Linux Test Project General Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-list-bounces@lists.sourceforge.net To: Andi Kleen Cc: ltp-list , linux-numa@vger.kernel.org On Mon, 7 Apr 2014, Andi Kleen wrote: > > * starts a binary with the specified numa memory policy using > > numactl (or a like): > > numactl --interleave=all get_some_memory_with_malloc_and_write_it > > * `sleep` for few seconds > > * numastat > /tmp/after > > * compares /tmp/before and /tmp/after to check that the numa policy > > was applied the right way > > > > But the problem is that on a host with many NUMA nodes (8) the process > > of updating that numastats statistics takes some time. Even 10 seconds > > may be not enough. Therefore the test fails. > > > > Is there a direct or indirect way to force the kernel to update the > > NUMA statistics? > > Not currently. It depends on how much memory you have and subsequent > operations. I guess would need to add one. The kernel vm statistics are brought up to date with the default settings every 2 seconds. The interval is controlled via /proc/sys/vm/stat_interval Check the value that you have setup there. ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees_APR _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Lameter Subject: Re: numastats updates Date: Mon, 7 Apr 2014 10:47:05 -0500 (CDT) Message-ID: References: <533D3BC7.8010309@oracle.com> <20140407013932.GU22728@two.firstfloor.org> Return-path: In-Reply-To: <20140407013932.GU22728@two.firstfloor.org> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1396885627; bh=skOZnRqh5l16YKUUv3eEYtwi8vWwFJSYmK55wfYa0vU=; h=Received:Received:Received:Received:Date:From:To:Subject: Message-ID:Content-Type; b=Vee4wl7w4mIBJtY2kLXTWybDoCTNojpely5sXddnqLB8elQQwZy7aHDzhLb58m5Mw RtYzFnW/BmLoR46RKEfWUY0o5gWVFDYimrCMvsdeUVewrdmvpdy7UCPlYlXkcuTLfg LDwLtsSpgAi92FuvI75lCb+K7CGa9fxvXYG74tYb6xmEkfvxGlzbOU3jri7Kr1hAQv ne2EjmPpGJgwP9IEMKeSq40cLMwCJScIh/n23y9SviglEo+whEuf5RoFfWohe4RVap 2NfGjhLaw2PZyvCO/zBHxPpoD4xMHbl3tV7JrG/HKID3qNA5VosCPkOWZLQ+3C5qQc 3erGS5z0qVieg== Sender: linux-numa-owner@vger.kernel.org List-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Andi Kleen Cc: Stanislav Kholmanskikh , linux-numa@vger.kernel.org, ltp-list On Mon, 7 Apr 2014, Andi Kleen wrote: > > * starts a binary with the specified numa memory policy using > > numactl (or a like): > > numactl --interleave=all get_some_memory_with_malloc_and_write_it > > * `sleep` for few seconds > > * numastat > /tmp/after > > * compares /tmp/before and /tmp/after to check that the numa policy > > was applied the right way > > > > But the problem is that on a host with many NUMA nodes (8) the process > > of updating that numastats statistics takes some time. Even 10 seconds > > may be not enough. Therefore the test fails. > > > > Is there a direct or indirect way to force the kernel to update the > > NUMA statistics? > > Not currently. It depends on how much memory you have and subsequent > operations. I guess would need to add one. The kernel vm statistics are brought up to date with the default settings every 2 seconds. The interval is controlled via /proc/sys/vm/stat_interval Check the value that you have setup there.