public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] kernel/numa: sleep 2s in test01 for waiting numastat updating
Date: Tue, 31 May 2016 18:45:05 +0200	[thread overview]
Message-ID: <20160531164504.GE14283@rei.lan> (raw)
In-Reply-To: <CAAUgArD-x-1w9GOg1gaExOiAGoFYwiRChMjB3GkNT+ZJh8Z+Tg@mail.gmail.com>

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...

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2016-05-31 16:45 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 [this message]
2016-07-05  1:22       ` Han Pingtian

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=20160531164504.GE14283@rei.lan \
    --to=chrubis@suse.cz \
    --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