From: Andi Kleen <andi@firstfloor.org>
To: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
Cc: linux-numa@vger.kernel.org,
ltp-list <ltp-list@lists.sourceforge.net>,
cl@linux-foundation.org
Subject: Re: numastats updates
Date: Mon, 7 Apr 2014 03:39:32 +0200 [thread overview]
Message-ID: <20140407013932.GU22728@two.firstfloor.org> (raw)
In-Reply-To: <533D3BC7.8010309@oracle.com>
On Thu, Apr 03, 2014 at 02:45:27PM +0400, Stanislav Kholmanskikh wrote:
> In LTP we have a test - numa01.sh (https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/numa/numa01.sh)
numactl has similar tests
>
> 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?
Not currently. It depends on how much memory you have and subsequent
operations. I guess would need to add one.
-Andi
next prev parent reply other threads:[~2014-04-07 1:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 10:45 numastats updates Stanislav Kholmanskikh
2014-04-07 1:39 ` Andi Kleen [this message]
2014-04-07 15:47 ` Christoph Lameter
2014-04-08 16:49 ` Stanislav Kholmanskikh
2014-04-08 16:57 ` Christoph Lameter
2014-04-08 16:58 ` Stanislav Kholmanskikh
2014-04-08 18:03 ` Christoph Lameter
2014-04-10 5:44 ` Stanislav Kholmanskikh
2014-04-11 1:48 ` Christoph Lameter
2014-04-11 2:12 ` Christoph Lameter
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=20140407013932.GU22728@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=linux-numa@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=stanislav.kholmanskikh@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).