From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] Hugetlb: Migrating libhugetlbfs shm-perms
Date: Wed, 6 Nov 2024 10:44:01 +0100 [thread overview]
Message-ID: <Zys6YRPAMzHDpMbo@yuki.lan> (raw)
In-Reply-To: <CAEemH2doMF7EggO_TOP+y=WwS75aXxrFA8mfaZmr-+YWwB1JSQ@mail.gmail.com>
Hi!
> > +static void compare_free_hugepage_memory(long free_end, long free_start)
> > +{
> > + if (free_end != free_start)
> > + tst_res(TFAIL, "Free hugepages after attaching multiple
> > threads differ from initial allocation");
> >
>
> We cannot make such an assumption for TFAIL because the system
> may be using hugepages in the background by other processes, and
> this test is not alone in occupying huge page so that would be possible
> get false positive in the real testing.
We already have similar assumptions in the rest of the hugepage tests,
however at least it's clear from the message that is being printed that
it may fail if we run more than one test in parallel or if system
allocates hugepages for something.
But I guess that we can do better, we can look at the HugetlbPages:
field in the "/proc/self/status" instead and check that it's incremented
and decremented properly as the test runs.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-11-06 9:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 13:40 [LTP] [PATCH v3] Hugetlb: Migrating libhugetlbfs shm-perms Spoorthy
2024-10-18 9:31 ` Li Wang
2024-11-06 9:44 ` Cyril Hrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 6:34 spoorthy s
2024-09-12 15:07 ` Cyril Hrubis
2024-09-11 10:41 spoorthy s
2024-09-11 14:14 ` Cyril Hrubis
2024-09-11 10:31 spoorthy s
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=Zys6YRPAMzHDpMbo@yuki.lan \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--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