From: Jan Stancek <jstancek@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Cyril Hrubis <chrubis@suse.cz>,
ltp@lists.linux.it, Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Tests for readahead() and fadvise() on overlayfs
Date: Mon, 8 Oct 2018 03:11:14 -0400 (EDT) [thread overview]
Message-ID: <1498422724.56763494.1538982674701.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20181004062624.27295-1-amir73il@gmail.com>
----- Original Message -----
> Cyril,
>
> The following series adds test covergae for readahead() syscall
> over overlayfs file and adds test coverage for a specific
> posix_fadvise() syscall advice (POSIX_FADV_WILLNEED).
>
> So far, the posix_fadvise syscall tests in LTP only test for error
> conditions, but not functionality.
>
> The functionality of the advice POSIX_FADV_WILLNEED is indentical
> to readahead() and since kernel commit 3d8f7615319b ("vfs: implement
> readahead(2) using POSIX_FADV_WILLNEED"), the implementations are
> also bound together.
>
> To add test coverage of the advice POSIX_FADV_WILLNEED, I decided not
> to duplicate the readahead() functional test and add test cases to
> readahead02 that use the POSIX_FADV_WILLNEED implementation.
>
> Thanks,
> Amir.
>
> Changes since v1:
> - Fix bugs in loop invocation of test (i.e. -i 2)
> - Address review comments from Jan Stancek
> - Make cached_max a global maximum over all test cases
> - Improve reliability of overlayfs readahead test case failure
Looks good to me.
When you say "This is the only system configuration supported by the posix_fadvise tests",
are you talking about glibc?
Regards,
Jan
>
> Amir Goldstein (5):
> syscalls/readahead01: Convert to newlib
> syscalls/readahead02: Convert to newlib and cleanup
> syscalls/readahead02: test readahead() on an overlayfs file
> syscalls/readahead02: test readahead using posix_fadvise()
> syscalls/readahead02: fail test if readahead did not use any cache
>
> .../kernel/syscalls/readahead/readahead01.c | 119 ++-----
> .../kernel/syscalls/readahead/readahead02.c | 333 +++++++++---------
> 2 files changed, 195 insertions(+), 257 deletions(-)
>
> --
> 2.17.1
>
>
next prev parent reply other threads:[~2018-10-08 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 6:26 [PATCH v2 0/5] Tests for readahead() and fadvise() on overlayfs Amir Goldstein
2018-10-04 6:26 ` [PATCH v2 1/5] syscalls/readahead01: Convert to newlib Amir Goldstein
2018-10-04 6:26 ` [PATCH v2 2/5] syscalls/readahead02: Convert to newlib and cleanup Amir Goldstein
2018-10-04 6:26 ` [PATCH v2 3/5] syscalls/readahead02: test readahead() on an overlayfs file Amir Goldstein
2018-10-04 6:26 ` [PATCH v2 4/5] syscalls/readahead02: test readahead using posix_fadvise() Amir Goldstein
2018-10-04 6:26 ` [PATCH v2 5/5] syscalls/readahead02: fail test if readahead did not use any cache Amir Goldstein
2018-10-08 7:11 ` Jan Stancek [this message]
2018-10-08 11:26 ` [PATCH v2 0/5] Tests for readahead() and fadvise() on overlayfs Amir Goldstein
2018-10-09 20:10 ` Amir Goldstein
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=1498422724.56763494.1538982674701.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=amir73il@gmail.com \
--cc=chrubis@suse.cz \
--cc=linux-unionfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=miklos@szeredi.hu \
/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).