From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Konstantin Khlebnikov <koct9i@gmail.com>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/vm: fix link error for transhuge-stress test
Date: Fri, 9 Jan 2015 00:30:06 +0300 [thread overview]
Message-ID: <20150108213006.GC2776@yulia-desktop> (raw)
In-Reply-To: <54AEA86D.60709@osg.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]
On Thu, Jan 08, 2015 at 08:55:25AM -0700, Shuah Khan wrote:
> On 01/07/2015 01:10 PM, Andrey Skvortsov wrote:
> > man page for clock_gettime says 'Link with -lrt'. So I think the
> > error message is correct.
> >
>
> Thanks for fixing it. Applied to linux-kselftest fixes branch
>
Hi Shuah,
thanks for taking the patch.
sorry for the late reply. I've just checked e-mail. Different
timezone. =)
I have couple questions about selftests/vm/hugetlbfstest. It is called by
make run_tests, but fails always on my machine.
What does it actually test? if I understand the code right,
it tests whether RSS (read from /proc/self/statm) grows/shrinks not much during
allocation/deallocation of 16Mb.
Here are couple of questions about some tests in the code.
1)
hugetlbfstest.c:75
do_mmap(-1, MAP_ANONYMOUS, 1);
it does not use hugetlbfs. So it does not correspond to the
actual test name. That confused me a little. Does it test usage of
transparent huge pages?
2)
hugetlbfstest.c:78
do_mmap(hugefd, 0, 1);
Despite the fact, that hugefd is open at wrong location
(run_tests script mounts hugetlbfs at ./huge) the test actually does
use hugetlbfs. Unfortunately on my machine it fails always too.
RSS does not grow after allocation, but is the same as before.
So assertion 'llabs(after - before - length) < 0x40000' fails.
But hugepages are definitely allocated, I can see that HugePages_Free decreases in
/proc/meminfo. To find this out I placed delays in the test code.
Does rss field in /proc/statm counts only normal non-huge pages?
--
Best regards,
Andrey Skvortsov
Secure e-mail with gnupg: See http://www.gnupg.org/
PGP Key ID: 0x57A3AEAD
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2015-01-08 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 18:35 [PATCH] selftests/vm: fix link error for transhuge-stress test Andrey Skvortsov
[not found] ` <1420655754-10076-1-git-send-email-Andrej.Skvortzov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-07 19:21 ` Shuah Khan
2015-01-07 20:10 ` Andrey Skvortsov
2015-01-08 15:55 ` Shuah Khan
2015-01-08 21:30 ` Andrey Skvortsov [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=20150108213006.GC2776@yulia-desktop \
--to=andrej.skvortzov@gmail.com \
--cc=koct9i@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkh@osg.samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).