From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/3] ltp/numa: waiting for numastat refresh
Date: Thu, 1 Dec 2016 11:51:29 +0100 [thread overview]
Message-ID: <20161201105129.GB5626@rei.lan> (raw)
In-Reply-To: <CAEemH2fRor7ORDSzfDf8podzjXc5jAYWn+L6d3kcudkW7kcGmg@mail.gmail.com>
Hi!
I've been looking into the problem and found much better solution. We
can, instead of quering the whole system statistic, read statistic for a
single process.
What about we do:
1. Change support_numa.c to sleep in wait() instead of exitting when
allocating memory
2. Run the numactl ... command on background with &
3. Then we can get statistic for a single process with numastat -p $pid
Alternatively we can change the support_numa.c to allocate the memory
with mmap and parse /proc/$pid/numa_maps to match the pointer address
and figure out if the mapping(s) are distributed correctly
4. Then we can kill the $pid
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2016-12-01 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 3:36 [LTP] [PATCH 1/3] ltp/numa: waiting for numastat refresh Li Wang
2016-11-23 12:57 ` Cyril Hrubis
2016-11-28 3:40 ` Li Wang
2016-12-01 10:51 ` Cyril Hrubis [this message]
2016-12-02 7:49 ` Li Wang
2016-12-05 9:28 ` Cyril Hrubis
2016-12-05 10:24 ` Li Wang
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=20161201105129.GB5626@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