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 4/4][RESEND] readahead: cleanup blockable_page_cache_readahead()
Date: Thu, 24 Feb 2005 16:32:05 -0600 [thread overview]
Message-ID: <421E55E5.3010404@austin.ibm.com> (raw)
In-Reply-To: <1109271683.6140.120.camel@localhost>
Ram wrote:
>Andrew,
> I have verified the patches against my standard benchmarks
> and did not see any bad effects.
>
> Also I have reviewd the patch and it looked clean and correct.
>
>RP
>
>
I have not had a chance to benchmark, but visual inspection looks good.
Steve
>On Thu, 2005-02-24 at 11:37, Oleg Nesterov wrote:
>
>
>>I think that do_page_cache_readahead() can be inlined
>>in blockable_page_cache_readahead(), this makes the
>>code a bit more readable in my opinion.
>>
>>Also makes check_ra_success() static inline.
>>
>>Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
>>
>>--- 2.6.11-rc5/mm/readahead.c~ 2005-01-29 15:51:04.000000000 +0300
>>+++ 2.6.11-rc5/mm/readahead.c 2005-01-29 16:37:05.000000000 +0300
>>@@ -348,8 +348,8 @@ int force_page_cache_readahead(struct ad
>> * readahead isn't helping.
>> *
>> */
>>-int check_ra_success(struct file_ra_state *ra, unsigned long nr_to_read,
>>- unsigned long actual)
>>+static inline int check_ra_success(struct file_ra_state *ra,
>>+ unsigned long nr_to_read, unsigned long actual)
>> {
>> if (actual == 0) {
>> ra->cache_hit += nr_to_read;
>>@@ -394,15 +394,11 @@ blockable_page_cache_readahead(struct ad
>> {
>> int actual;
>>
>>- if (block) {
>>- actual = __do_page_cache_readahead(mapping, filp,
>>- offset, nr_to_read);
>>- } else {
>>- actual = do_page_cache_readahead(mapping, filp,
>>- offset, nr_to_read);
>>- if (actual == -1)
>>- return 0;
>>- }
>>+ if (!block && bdi_read_congested(mapping->backing_dev_info))
>>+ return 0;
>>+
>>+ actual = __do_page_cache_readahead(mapping, filp, offset, nr_to_read);
>>+
>> return check_ra_success(ra, nr_to_read, actual);
>> }
>>
>>
prev parent reply other threads:[~2005-02-24 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 19:37 [PATCH 4/4][RESEND] readahead: cleanup blockable_page_cache_readahead() Oleg Nesterov
2005-02-24 19:01 ` Ram
2005-02-24 22:32 ` Steven Pratt [this message]
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=421E55E5.3010404@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