From: Steven Pratt <slpratt@austin.ibm.com>
To: Ram <linuxram@us.ibm.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/4] page_cache_readahead: remove duplicated code
Date: Tue, 25 Jan 2005 18:16:53 -0600 [thread overview]
Message-ID: <41F6E175.9000502@austin.ibm.com> (raw)
In-Reply-To: <1106698119.3298.57.camel@localhost>
Ram wrote:
>On Tue, 2005-01-25 at 03:59, Oleg Nesterov wrote:
>
>
>>Cases "no ahead window" and "crossed into ahead window"
>>can be unified.
>>
>>
>
>
>No. There is a reason why we had some duplication. With your patch,
>we will end up reading-on-demand instead of reading ahead.
>
>When we notice a sequential reads have resumed, we first read in the
>data that is requested.
>However if the read request is for more pages than what are being held
>in the current window, we make the ahead window as the current window
>and read in more pages in the ahead window. Doing that gives the
>opportunity of always having pages in the ahead window when the next
>sequential read request comes in. If we apply this patch, we will
>always have to read the pages that are being requested instead of
>satisfying them from the ahead window.
>
>
Ah, you are right!
>Ok, if this does not make it clear, here is another way of proving that
>your patch does not exactly behave the way it did earlier.
>
>With your patch you will have only one call to
>block_page_cache_readahead(), when earlier there could be cases where
>block_page_cache_readahead() could be called twice.
>
>Am I am making sense?
>
Completely, this patch should not be applied. Good catch.
Steve
>RP
>
>
>
next prev parent reply other threads:[~2005-01-26 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 11:59 [PATCH 2/4] page_cache_readahead: remove duplicated code Oleg Nesterov
2005-01-25 21:46 ` Steven Pratt
2005-01-26 0:08 ` Ram
2005-01-26 0:16 ` Steven Pratt [this message]
2005-01-26 12:02 ` Oleg Nesterov
2005-01-28 20:13 ` Ram
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=41F6E175.9000502@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=oleg@tv-sign.ru \
/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