All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH] nfs: remove redundant tests on reading new pages
Date: Mon, 1 Dec 2008 11:31:09 +0800	[thread overview]
Message-ID: <20081201033109.GA31253@localhost> (raw)
In-Reply-To: <20081201031922.GA31077@localhost>

On Mon, Dec 01, 2008 at 11:19:22AM +0800, Wu Fengguang wrote:
> aops->readpages() and its NFS helper readpage_async_filler() will only
> be called to do readahead I/O for newly allocated pages. So it's not
> necessary to test for the always 0 dirty/uptodate page flags.
> 
> The removal of nfs_wb_page() call also fixes a readahead bug: the NFS
> readahead has been synchronous since 2.6.23, because that call will
> clear PG_readahead, which is the reminder for asynchronous readahead.
> 
> More background: the PG_readahead page flag is shared with PG_reclaim,
> one for read path and the other for write path. clear_page_dirty_for_io()
> unconditionally clears PG_readahead to prevent possible readahead residuals,
> assuming itself to be always called in the write path. However, NFS is one
> and the only exception in that it _always_ calls clear_page_dirty_for_io()
> in the read path, i.e. for readpages()/readpage().
> 
> Cc: Trond Myklebust <Trond.Myklebust@netapp.com>
> Signed-off-by: Wu Fengguang <wfg@linux.intel.com>
> ---
>  fs/nfs/read.c |    6 ------
>  1 file changed, 6 deletions(-)
> 
> This bug was found when playing with my readahead tracing module posted at
> http://lkml.org/lkml/2008/11/27/373 and confirmed to work.
> 
> The NFS readahead traces are now
> 
> [   59.972526] readahead-initial0(pid=3646(dd), dev=00:0f(0:f), ino=293189(1G), req=0+25, ra=0+60-30, async=0) = 60
> [   59.992734] readahead-subsequent(pid=3646(dd), dev=00:0f(0:f), ino=293189(1G), req=30+20, ra=60+30-30, async=1) = 30
> [   60.030900] readahead-subsequent(pid=3646(dd), dev=00:0f(0:f), ino=293189(1G), req=60+15, ra=90+30-30, async=1) = 30
> [   60.031687] readahead-subsequent(pid=3646(dd), dev=00:0f(0:f), ino=293189(1G), req=90+10, ra=120+30-30, async=1) = 30
> 
> The async field was always 0 before this patch.

On the trace messages: they are generated by the command
'dd if=/tmp/sparse/1G of=/dev/null bs=100k count=9' with readahead_size=120k.

The printk for generating the messages is:

        printk(KERN_DEBUG "readahead-%s(pid=%d(%s), dev=%02x:%02x(%s), "
                "ino=%lu(%s), req=%lu+%lu, ra=%lu+%d-%d, async=%d) = %d\n",
                ra_pattern_names[pattern],
                current->pid, current->comm,
                MAJOR(mapping->host->i_sb->s_dev),
                MINOR(mapping->host->i_sb->s_dev),
                mapping->host->i_sb->s_id,
                mapping->host->i_ino,
                filp->f_path.dentry->d_name.name,
                offset, req_size,
                ra->start, ra->size, ra->async_size,
                async,
                actual);

Thanks,
Fengguang

> --- linux-2.6.orig/fs/nfs/read.c
> +++ linux-2.6/fs/nfs/read.c
> @@ -533,12 +533,6 @@ readpage_async_filler(void *data, struct
>  	unsigned int len;
>  	int error;
>  
> -	error = nfs_wb_page(inode, page);
> -	if (error)
> -		goto out_unlock;
> -	if (PageUptodate(page))
> -		goto out_unlock;
> -
>  	len = nfs_page_length(page);
>  	if (len == 0)
>  		return nfs_return_empty_page(page);

      reply	other threads:[~2008-12-01  3:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01  3:19 [PATCH] nfs: remove redundant tests on reading new pages Wu Fengguang
2008-12-01  3:31 ` Wu Fengguang [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=20081201033109.GA31253@localhost \
    --to=fengguang.wu@intel.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stable@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.