From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
Subject: numastats updates
Date: Thu, 03 Apr 2014 14:45:27 +0400
Message-ID: <533D3BC7.8010309@oracle.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-numa-owner@vger.kernel.org>
Sender: linux-numa-owner@vger.kernel.org
List-ID: <linux-numa.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: linux-numa@vger.kernel.org
Cc: ltp-list <ltp-list@lists.sourceforge.net>

Hello!

In LTP we have a test - numa01.sh 
(https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/numa/numa01.sh)

In general, this script does something like:
   * numastat > /tmp/before
   * 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?

Thank you.