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 v2] move_pages12: Make sure hugepages are available
Date: Tue, 16 May 2017 15:32:33 +0200	[thread overview]
Message-ID: <20170516133233.GB2897@rei.lan> (raw)
In-Reply-To: <1420231349.12458178.1494937684196.JavaMail.zimbra@redhat.com>

Hi!
> "hugepages-2048kB" in path above will work only on systems with 2M huge pages.

Do you have a ppc64 numa machine with more than two nodes at hand? Since
that is the only one where the current code may fail. Both x86_64 and
aarch64 seems to have 2MB huge pages.

I would just go with this patch now, and possibly fix more complicated
corner cases after the release, since this patch is the last problem
that holds the release from my side.

Anything else that should be taken care of before the release?

> > +
> > +	if (!access(path_hugepages_node1, F_OK)) {
> > +		SAFE_FILE_SCANF(path_hugepages_node1,
> > +				"%ld", &orig_hugepages_node1);
> > +		tst_res(TINFO, "Increasing hugepages pool on node %u to %ld",
> > +			node1, orig_hugepages_node1 + 4);
> > +		SAFE_FILE_PRINTF(path_hugepages_node1,
> > +				 "%ld", orig_hugepages_node1 + 4);
> 
> There doesn't seem to be any error if you ask for more:
> 
> # echo 20000 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
> # cat /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
> 11650
> 
> So, maybe we can just read it back and if it doesn't match what we requested,
> we can TCONF.

Or we may try to allocate 4 huge pages on both nodes even in a case that
we set the per-node limits that should catch the problem as well. Is
that OK with you?

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2017-05-16 13:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 10:07 [LTP] [PATCH v2] move_pages12: Make sure hugepages are available Cyril Hrubis
2017-05-16 12:28 ` Jan Stancek
2017-05-16 13:32   ` Cyril Hrubis [this message]
2017-05-16 14:05     ` Jan Stancek
2017-05-16 14:15       ` Cyril Hrubis
2017-05-16 14:15       ` Jan Stancek
2017-05-16 14:29         ` Cyril Hrubis
2017-05-17  8:21           ` Jan Stancek
2017-05-29 13:12           ` Jan Stancek
2017-05-29 13:45             ` Jan Stancek
2017-05-30 11:50             ` Cyril Hrubis
2017-05-30 13:11               ` Jan Stancek
2017-05-30 13:48                 ` Cyril Hrubis
2017-05-31  7:46                   ` Jan Stancek

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=20170516133233.GB2897@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