From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Peng Tao <bergwolf@gmail.com>
Cc: linux-nfs@vger.kernel.org, mdw@umich.edu, honey@citi.umich.edu,
Peng Tao <peng_tao@emc.com>, Benny Halevy <bhalevy@tonian.com>
Subject: Re: [PATCH-v2 3/9] pnfsblock: move find lock page logic out of bl_write_pagelist
Date: Thu, 12 Jan 2012 16:44:57 -0500 [thread overview]
Message-ID: <1326404697.10529.1.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1326381528-2232-4-git-send-email-bergwolf@gmail.com>
On Thu, 2012-01-12 at 23:18 +0800, Peng Tao wrote:
> Also avoid unnecessary lock_page if page is handled by others.
Ditto...
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2012-01-12 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 15:18 [PATCH-v2 0/9] pnfsblock patches for 3.3 post-rc1 Peng Tao
2012-01-12 15:18 ` [PATCH-v2 1/9] pnfsblock: cleanup bl_mark_sectors_init Peng Tao
2012-01-12 21:44 ` Trond Myklebust
2012-01-13 2:38 ` tao.peng
2012-01-12 15:18 ` [PATCH-v2 3/9] pnfsblock: move find lock page logic out of bl_write_pagelist Peng Tao
2012-01-12 21:44 ` Trond Myklebust [this message]
2012-01-12 15:18 ` [PATCH-v2 4/9] pnfsblock: set read/write tk_status to pnfs_error Peng Tao
2012-01-12 15:18 ` [PATCH-v2 5/9] pnfsblock: remove rpc_call_ops from struct parallel_io Peng Tao
2012-01-12 21:45 ` Trond Myklebust
2012-01-12 15:18 ` [PATCH-v2 6/9] pnfsblock: clean up _add_entry Peng Tao
2012-01-12 15:18 ` [PATCH-v2 7/9] pnfsblock: alloc short extent before submit bio Peng Tao
2012-01-12 21:45 ` Trond Myklebust
2012-01-12 15:26 ` [PATCH-v2 0/9] pnfsblock patches for 3.3 post-rc1 Peng Tao
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=1326404697.10529.1.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=bergwolf@gmail.com \
--cc=bhalevy@tonian.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=mdw@umich.edu \
--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;
as well as URLs for NNTP newsgroup(s).