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] [RFC] [PATCH] move_pages12: Allocate and free hugepages prior	the test
Date: Thu, 11 May 2017 14:26:36 +0200	[thread overview]
Message-ID: <20170511122636.GA27575@rei.lan> (raw)
In-Reply-To: <57874670.10114549.1494484804573.JavaMail.zimbra@redhat.com>

Hi!
> > Well that is a few forks away after the failure, if the race window is
> > small enough we will never see the real value but maybe doing open() and
> > read() directly would show us different values.
> 
> For free/reserved, sure. But is the number of reserved huge pages on
> each node going to change over time?

Of course I was speaking about the number of currently free huge pages.
The pool limit will not change unless something from userspace writes to
the sysfs file...

> ---
> 
> I was running with 20+20 huge pages over night and it hasn't failed
> single time. So I'm thinking we allocate 3+3 or 4+4 to avoid any
> issues related to lazy/deffered updates.

But we have to lift the per node limits as well, right?

So what about lifting the per node limit to something as 20 and then try
to allocate 4 hugepages on each node prior the test?

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2017-05-11 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 14:04 [LTP] [RFC] [PATCH] move_pages12: Allocate and free hugepages prior the test Cyril Hrubis
2017-05-10  8:56 ` Jan Stancek
2017-05-10 12:21   ` Cyril Hrubis
2017-05-10 13:01     ` Jan Stancek
2017-05-10 13:49   ` Cyril Hrubis
2017-05-10 14:14     ` Jan Stancek
2017-05-10 15:08       ` Cyril Hrubis
2017-05-11  6:40         ` Jan Stancek
2017-05-11 12:26           ` Cyril Hrubis [this message]
2017-05-11 12:50             ` Jan Stancek
2017-05-16  9:30               ` Cyril Hrubis

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=20170511122636.GA27575@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