From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] kernel/numa: sleep 2s in test01 for waiting numastat updating
Date: Tue, 5 Jul 2016 09:22:36 +0800 [thread overview]
Message-ID: <20160705012236.GA3581@localhost.localdomain> (raw)
In-Reply-To: <20160531164504.GE14283@rei.lan>
On Tue, May 31, 2016 at 06:45:05PM +0200, Cyril Hrubis wrote:
> Hi!
> > > What we should do instead is to get the new stastistic in loop with a
> > > short (~0.1s) sleep util we get the expected value or until timeout has
> > > been reached (~10s). And this should be done ideally as a function
> > > called from each of the numa tests.
> > >
> >
> > I think we should not wait for 10s, it is a bit longer, the test will
> > pass no matter we
> > add "numactl --cpunodebind=$node --membind=$node support_numa
> > $ALLOC_1MB" or not.
>
> Hmm, we are looking at accumulated statistics. So some of the tests will
> just pass as other processes allocate memory as well.
>
> > I suppose maybe we could refine the support_numa to make it allocate
> > a bigger memory and run for a while rather than return immediately.
>
> I wonder if there is a file in /proc/ that could be used to determine on
> which numa node is the page allocated on. There is /proc/$pid/pagemap
> that could be used to map address to someting that could used to seek in
> /proc/kpageflags that can be used to get quite a lot of information
> about the page state but not on which numa node it is allocated on...
>
On two systems with two different beta distros, test01 always fail even
after adding 'sleep 2s'. Looks like there is no guarantee when naumstat
will be updated at all.
One distro uses a 4.4.13 kernel, the other uses a 4.4.0 kernel.
prev parent reply other threads:[~2016-07-05 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 9:56 [LTP] [PATCH] kernel/numa: sleep 2s in test01 for waiting numastat updating Dong ZHu
2016-05-30 11:55 ` Cyril Hrubis
2016-05-31 1:08 ` Dong ZHu
2016-05-31 16:45 ` Cyril Hrubis
2016-07-05 1:22 ` Han Pingtian [this message]
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=20160705012236.GA3581@localhost.localdomain \
--to=hanpt@linux.vnet.ibm.com \
--cc=ltp@lists.linux.it \
/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