From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] [RFC] syscalls/mmap12: Do not fail on non-present pages
Date: Fri, 18 Aug 2017 06:00:54 -0400 (EDT) [thread overview]
Message-ID: <1932775025.3810596.1503050454745.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170817143310.11634-2-chrubis@suse.cz>
----- Original Message -----
> There are two problems with the testcase:
>
> 1. MAP_POPULATE is best effort operation.
>
> To quote Michal Hocko:
>
> "The semantic of MAP_POPULATE is rather vague and allows for nuances
> in future."
>
> 2. There is no guarantee that the pages will be present even if
> MAP_POPULATE caused read-ahead.
>
> To quote Michal again:
>
> "Ptes can be made !present, reclaimed or who knows what else in
> future yet that won't qualify as a regression. I find such a test
> questionable at best."
Hi,
I agree with points 1 and 2, the test relies on likely
scenario that pages were present. We are in similar
situation when it comes to readahead test.
@Michal: Can you think of alternative way to differentiate between:
"MAP_POPULATE did its best" vs. "MAP_POPULATE is broken"?
>
> I still think that calling mmap() with MAP_POPULATE and checking that
> the mapping is OK is a valid testcase itself, so instead of passing the
> test on present pages we simply check that the mapping is zero-filled
> (since we mapped empty file). I kept the page-present check still there
> but it now produces only INFO messages, it could be removed though if
> everyone agrees that it has no real value.
Agreed, we should have at least test that uses the flag - so we can
tell it didn't have negative impact (Oops/non-zero values mapped/etc).
Regards,
Jan
next prev parent reply other threads:[~2017-08-18 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:33 [LTP] [PATCH 1/2] [COMMITTED] syscalls/mmap12: Convert to the new library Cyril Hrubis
2017-08-17 14:33 ` [LTP] [PATCH 2/2] [RFC] syscalls/mmap12: Do not fail on non-present pages Cyril Hrubis
2017-08-18 10:00 ` Jan Stancek [this message]
2017-08-18 13:50 ` Michal Hocko
2017-09-14 11:44 ` Cyril Hrubis
2017-09-14 14:08 ` Jan Stancek
2017-09-14 15:05 ` 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=1932775025.3810596.1503050454745.JavaMail.zimbra@redhat.com \
--to=jstancek@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