From: Oleg Nesterov <oleg@tv-sign.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linuxram@us.ibm.com,
slpratt@austin.ibm.com
Subject: Re: [PATCH 1/2] readahead: simplify ra->size testing
Date: Thu, 03 Mar 2005 13:08:42 +0300 [thread overview]
Message-ID: <4226E22A.2526DE09@tv-sign.ru> (raw)
In-Reply-To: 20050302175947.6f1e6b5f.akpm@osdl.org
Andrew Morton wrote:
>
> So... the big "how it all works" comment needs an update..
Same patch, comment updated.
Currently page_cache_readahead() treats ra->size == 0 (first read)
and ra->size == -1 (ra_off was called) separately, but does exactly
the same in both cases.
With this patch we may assume that the reading starts in 'ra_off()'
state, so we don't need to consider the first read as a special case.
file_ra_state_init() sets
ra->prev_page = -1;
ra->size = 0;
When the page_cache_readahead() is called for the first time it sets
ra->size to nonzero value either via get_init_ra_size() or ra_off().
So ra->size == 0 implies that ra->prev_page == -1. I am ignoring the
case when readahead is disabled via ra->ra_pages == 0.
page_cache_readahead detects sub-page sized reads:
if (offset == ra->prev_page && req_size == 1 && ra->size != 0)
But if offset == ra->prev_page, then ra->size == 0 can happen only if
offset == -1, so there is no need to check ra->size here. If application
starts reading 16Tb file from the last page then readahead can't help.
First offset==0 read or first sequential detection:
if ((ra->size == 0 && offset == 0) || (ra->size == -1 && sequential)
could be changed to:
if ((ra->size == 0 && sequential) || (ra->size == -1 && sequential)
which means:
if (sequential && (ra->size == 0 || ra->size == -1))
Random case detection:
if (!sequential || (ra->size == 0))
But if sequential == 1, then ra->size can't be 0, this case is already handled
before.
Now we have:
if (offset == ra->prev_page && req_size == 1)
/* sub-page reads */
if (sequential && (ra->size == 0 || ra->size == -1))
/* first offset==0 read or first sequential */
if (!sequential)
/* random case */
Now ->size is checked only in one place, so ra_off() can set ra->size = 0,
and we can just test ->size against 0.
Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
--- 2.6.11/mm/readahead.c~ 2005-02-04 21:33:40.000000000 +0300
+++ 2.6.11/mm/readahead.c 2005-02-04 21:33:57.000000000 +0300
@@ -55,7 +55,7 @@ static inline void ra_off(struct file_ra
{
ra->start = 0;
ra->flags = 0;
- ra->size = -1;
+ ra->size = 0;
ra->ahead_start = 0;
ra->ahead_size = 0;
return;
@@ -452,7 +452,7 @@ page_cache_readahead(struct address_spac
* perturbing the readahead window expansion logic.
* If size is zero, there is no read ahead window so we need one
*/
- if (offset == ra->prev_page && req_size == 1 && ra->size != 0)
+ if (offset == ra->prev_page && req_size == 1)
goto out;
ra->prev_page = offset;
@@ -471,9 +471,7 @@ page_cache_readahead(struct address_spac
* at start of file, and grow the window fast. Or detect first
* sequential access
*/
- if ((ra->size == 0 && offset == 0) /* first io and start of file */
- || (ra->size == -1 && sequential)) {
- /* First sequential */
+ if (sequential && ra->size == 0) {
ra->size = get_init_ra_size(newsize, max);
ra->start = offset;
if (!blockable_page_cache_readahead(mapping, filp, offset,
@@ -499,7 +497,7 @@ page_cache_readahead(struct address_spac
* partial page reads and first access were handled above,
* so this must be the next page otherwise it is random
*/
- if (!sequential || (ra->size == 0)) {
+ if (!sequential) {
ra_off(ra);
blockable_page_cache_readahead(mapping, filp, offset,
newsize, ra, 1);
next prev parent reply other threads:[~2005-03-03 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 19:08 [PATCH 1/2] readahead: simplify ra->size testing Oleg Nesterov
2005-03-03 1:59 ` Andrew Morton
2005-03-03 10:08 ` Oleg Nesterov [this message]
2005-03-03 9:28 ` Andrew Morton
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=4226E22A.2526DE09@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=slpratt@austin.ibm.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