From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
To: ltp-list <ltp-list@lists.sourceforge.net>
Cc: Vasily Isaenko <vasily.isaenko@oracle.com>
Subject: [LTP] numa01
Date: Mon, 31 Mar 2014 11:59:26 +0400 [thread overview]
Message-ID: <5339205E.30801@oracle.com> (raw)
Hi!
numa01.sh does something like:
* numastat > /tmp/before
* starts a binary with the specified 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.
Does anybody know if there is a direct or indirect way to force the
kernel to update the NUMA statistics?
Thank you.
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2014-03-31 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 7:59 Stanislav Kholmanskikh [this message]
2014-03-31 12:31 ` [LTP] numa01 chrubis
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=5339205E.30801@oracle.com \
--to=stanislav.kholmanskikh@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vasily.isaenko@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 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.