public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@tonian.com>
To: Peng Tao <bergwolf@gmail.com>
Cc: linux-nfs@vger.kernel.org, Trond.Myklebust@netapp.com,
	Peng Tao <peng_tao@emc.com>
Subject: Re: [PATCH 3/8] pnfsblock: move find lock page logic out of bl_write_pagelist
Date: Thu, 10 Nov 2011 10:32:20 +0200	[thread overview]
Message-ID: <4EBB8C14.2090209@tonian.com> (raw)
In-Reply-To: <1320851766-1834-4-git-send-email-bergwolf@gmail.com>

On 2011-11-09 17:16, Peng Tao wrote:
> Also avoid unnecessary lock_page if page is handled by others.
> 
> Signed-off-by: Peng Tao <peng_tao@emc.com>
> ---
>  fs/nfs/blocklayout/blocklayout.c |   78 ++++++++++++++++++++++++++------------
>  1 files changed, 54 insertions(+), 24 deletions(-)
> 
> diff --git a/fs/nfs/blocklayout/blocklayout.c b/fs/nfs/blocklayout/blocklayout.c
> index 4ced0b0..e8e13f3 100644
> --- a/fs/nfs/blocklayout/blocklayout.c
> +++ b/fs/nfs/blocklayout/blocklayout.c
> @@ -484,6 +484,56 @@ cleanup:
>  	return ret;
>  }
>  
> +/* Find or create a zeroing page marked being writeback.
> + * Return ERR_PTR on error, NULL to indicate skip this page and page itself
> + * to indicate write out.
> + */
> +static struct page*

coding style nit: "page *" rather than "page*"

> +bl_find_get_zeroing_page(struct inode *inode, pgoff_t index,
> +			struct pnfs_block_extent *cow_read)
> +{
> +	struct page* page;

checkpatch nit:
ERROR: "foo* bar" should be "foo *bar"

> +	int locked = 0;
> +	page = find_get_page(inode->i_mapping, index);
> +	if (page)
> +		goto check_page;
> +
> +	page = find_or_create_page(inode->i_mapping, index, GFP_NOFS);
> +	if (unlikely(!page)) {
> +		dprintk("%s oom\n", __func__);
> +		return ERR_PTR(-ENOMEM);
> +	}
> +	locked = 1;

Why not just call find_or_create_page in the first place?
dealing with both the locked and unlocked cases here just
seems to add unneeded complexity.

Benny

> +
> +check_page:
> +	/* PageDirty: Other will write this out
> +	 * PageWriteback: Other is writing this out
> +	 * PageUptodate: It was read before
> +	 */
> +	if (PageDirty(page) || PageWriteback(page)) {
> +		print_page(page);
> +		if (locked)
> +			unlock_page(page);
> +		page_cache_release(page);
> +		return NULL;
> +	}
> +
> +	if (!locked) {
> +		lock_page(page);
> +		if (PageDirty(page) || PageWriteback(page))
> +			unlock_page(page);
> +		return NULL;
> +	}
> +	if (!PageUptodate(page)) {
> +		/* New page, readin or zero it */
> +		init_page_for_write(page, cow_read);
> +	}
> +	set_page_writeback(page);
> +	unlock_page(page);
> +
> +	return page;
> +}
> +
>  static enum pnfs_try_status
>  bl_write_pagelist(struct nfs_write_data *wdata, int sync)
>  {
> @@ -543,32 +593,12 @@ fill_invalid_ext:
>  			dprintk("%s zero %dth page: index %lu isect %llu\n",
>  				__func__, npg_zero, index,
>  				(unsigned long long)isect);
> -			page =
> -			    find_or_create_page(wdata->inode->i_mapping, index,
> -						GFP_NOFS);
> -			if (!page) {
> -				dprintk("%s oom\n", __func__);
> -				wdata->pnfs_error = -ENOMEM;
> +			page = bl_find_get_zeroing_page(wdata->inode, index, cow_read);
> +			if (unlikely(IS_ERR(page))) {
> +				wdata->pnfs_error = PTR_ERR(page);
>  				goto out;
> -			}
> -
> -			/* PageDirty: Other will write this out
> -			 * PageWriteback: Other is writing this out
> -			 * PageUptodate: It was read before
> -			 * sector_initialized: already written out
> -			 */
> -			if (PageDirty(page) || PageWriteback(page)) {
> -				print_page(page);
> -				unlock_page(page);
> -				page_cache_release(page);
> +			} else if (page == NULL)
>  				goto next_page;
> -			}
> -			if (!PageUptodate(page)) {
> -				/* New page, readin or zero it */
> -				init_page_for_write(page, cow_read);
> -			}
> -			set_page_writeback(page);
> -			unlock_page(page);
>  
>  			ret = bl_mark_sectors_init(be->be_inval, isect,
>  						       PAGE_CACHE_SECTORS);

  reply	other threads:[~2011-11-10  8:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 15:15 [PATCH 0/8] pnfsblock cleanup and fixes Peng Tao
2011-11-09 15:15 ` [PATCH 1/8] pnfsblock: cleanup bl_mark_sectors_init Peng Tao
2011-11-09 15:16 ` [PATCH 3/8] pnfsblock: move find lock page logic out of bl_write_pagelist Peng Tao
2011-11-10  8:32   ` Benny Halevy [this message]
2011-11-10  8:49     ` tao.peng
2011-11-10  9:31       ` Benny Halevy
2011-11-10  9:40         ` tao.peng
2011-11-09 15:16 ` [PATCH 4/8] pnfsblock: set read/write tk_status to pnfs_error Peng Tao
2011-11-09 15:16 ` [PATCH 5/8] pnfsblock: remove rpc_call_ops from struct parallel_io Peng Tao
2011-11-09 15:16 ` [PATCH 6/8] pnfsblock: clean up _add_entry Peng Tao
2011-11-10  8:44   ` Benny Halevy
2011-11-10  8:56     ` tao.peng
2011-11-10  9:11     ` tao.peng
2011-11-09 15:16 ` [PATCH 7/8] pnfsblock: add im_extents to pnfs_inval_markings Peng Tao
2011-11-10  8:54   ` Benny Halevy
2011-11-10  9:08     ` tao.peng
2011-11-10  9:37       ` Benny Halevy
2011-11-10  9:20     ` Benny Halevy
2011-11-10  9:37       ` tao.peng
2011-11-10  9:39         ` Benny Halevy
2011-11-09 15:16 ` [PATCH 8/8] pnfsblock: alloc short extent before submit bio Peng Tao
2011-11-10  9:22   ` Benny Halevy
2011-11-10  2:09 ` [PATCH 0/8] pnfsblock cleanup and fixes tao.peng
2011-11-10  7:06   ` Benny Halevy
2011-11-10  8:37 ` Benny Halevy
2011-11-10  8:51   ` tao.peng

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=4EBB8C14.2090209@tonian.com \
    --to=bhalevy@tonian.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bergwolf@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=peng_tao@emc.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