From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: ltp@lists.linux.it
Subject: [LTP] [bug report] readahead02: readahead hardcoded bytes limit
Date: Fri, 11 Dec 2015 13:53:23 +0000 [thread overview]
Message-ID: <20151211135323.GA31048@red-moon> (raw)
Hi,
following kernel commit:
commit 600e19afc5f8a6 ("mm: use only per-device readahead limit")
LTP readahead02 test produces warnings such as:
readahead02 0 TINFO : creating test file of size: 67108864#
readahead02 (1698): drop_caches: 1#
readahead02 0 TINFO : read_testfile(0)#
readahead02 (1698): drop_caches: 1#
readahead02 0 TINFO : read_testfile(1)#
readahead02 1 TPASS : expected ret success - returned value = 0#
readahead02 2 TPASS : offset is still at 0 as expected#
readahead02 0 TINFO : read_testfile(0) took: 125319 usec#
readahead02 0 TINFO : read_testfile(1) took: 119364 usec#
readahead02 0 TINFO : read_testfile(0) read: 67357696 bytes#
readahead02 0 TINFO : read_testfile(1) read: 63098880 bytes#
readahead02 3 TPASS : readahead saved some I/O#
readahead02 0 TINFO : cache can hold at least: 67372 kB#
readahead02 0 TINFO : read_testfile(0) used cache: 65420 kB#
readahead02 0 TINFO : read_testfile(1) used cache: 4120 kB#
readahead02 0 TWARN : readahead02.c:323: using less cache than expected
It is caused by the hardcoded 2MB readahead02 limit used to issue
the readahead syscall, the kernel now caps the number of pages
using the per-device readahead limit, so the readahead count parameter
should be updated accordingly.
There are multiple ways to fix it, simplest is reading the bdi backing
the testfile and use its readahead limit as readahead syscall count
parameter.
Please consider updating the test.
Thanks,
Lorenzo
next reply other threads:[~2015-12-11 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:53 Lorenzo Pieralisi [this message]
2015-12-11 15:07 ` [LTP] [bug report] readahead02: readahead hardcoded bytes limit Roman Gushchin
2015-12-21 13:21 ` [LTP] [PATCH] syscalls/readahead02: fix error check Roman Gushchin
2016-01-04 9:41 ` Jan Stancek
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=20151211135323.GA31048@red-moon \
--to=lorenzo.pieralisi@arm.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