From: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: v9fs-developer@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [V9fs-developer] [PATCH 2/5] fs/9p: Use write_inode for data sync on server
Date: Fri, 25 Mar 2011 13:49:32 -0700 [thread overview]
Message-ID: <4D8CFFDC.7010409@linux.vnet.ibm.com> (raw)
In-Reply-To: <1301052651-21440-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On 03/25/2011 04:30 AM, Aneesh Kumar K.V wrote:
> Signed-off-by: Aneesh Kumar K.V<aneesh.kumar@linux.vnet.ibm.com>
Reviewed-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
> ---
> fs/9p/vfs_super.c | 43 +++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 43 insertions(+), 0 deletions(-)
>
> diff --git a/fs/9p/vfs_super.c b/fs/9p/vfs_super.c
> index f3eed33..d94adcb 100644
> --- a/fs/9p/vfs_super.c
> +++ b/fs/9p/vfs_super.c
> @@ -307,6 +307,47 @@ static int v9fs_drop_inode(struct inode *inode)
> return 1;
> }
>
> +static int v9fs_write_inode(struct inode *inode,
> + struct writeback_control *wbc)
> +{
> + int ret;
> + struct p9_wstat wstat;
> + struct v9fs_inode *v9inode;
> + /*
> + * send an fsync request to server irrespective of
> + * wbc->sync_mode.
> + */
> + P9_DPRINTK(P9_DEBUG_VFS, "%s: inode %p\n", __func__, inode);
> + v9inode = V9FS_I(inode);
> + v9fs_blank_wstat(&wstat);
> +
> + ret = p9_client_wstat(v9inode->writeback_fid,&wstat);
> + if (ret< 0) {
> + __mark_inode_dirty(inode, I_DIRTY_DATASYNC);
> + return ret;
> + }
> + return 0;
> +}
> +
> +static int v9fs_write_inode_dotl(struct inode *inode,
> + struct writeback_control *wbc)
> +{
> + int ret;
> + struct v9fs_inode *v9inode;
> + /*
> + * send an fsync request to server irrespective of
> + * wbc->sync_mode.
> + */
> + P9_DPRINTK(P9_DEBUG_VFS, "%s: inode %p\n", __func__, inode);
> + v9inode = V9FS_I(inode);
> + ret = p9_client_fsync(v9inode->writeback_fid, 0);
> + if (ret< 0) {
> + __mark_inode_dirty(inode, I_DIRTY_DATASYNC);
> + return ret;
> + }
> + return 0;
> +}
> +
> static const struct super_operations v9fs_super_ops = {
> .alloc_inode = v9fs_alloc_inode,
> .destroy_inode = v9fs_destroy_inode,
> @@ -314,6 +355,7 @@ static const struct super_operations v9fs_super_ops = {
> .evict_inode = v9fs_evict_inode,
> .show_options = generic_show_options,
> .umount_begin = v9fs_umount_begin,
> + .write_inode = v9fs_write_inode,
> };
>
> static const struct super_operations v9fs_super_ops_dotl = {
> @@ -325,6 +367,7 @@ static const struct super_operations v9fs_super_ops_dotl = {
> .evict_inode = v9fs_evict_inode,
> .show_options = generic_show_options,
> .umount_begin = v9fs_umount_begin,
> + .write_inode = v9fs_write_inode_dotl,
> };
>
> struct file_system_type v9fs_fs_type = {
next prev parent reply other threads:[~2011-03-25 20:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 11:30 [PATCH 1/5] fs/9p: Fix revalidate to return correct value Aneesh Kumar K.V
2011-03-25 11:30 ` [PATCH 2/5] fs/9p: Use write_inode for data sync on server Aneesh Kumar K.V
2011-03-25 20:49 ` Venkateswararao Jujjuri [this message]
2011-03-25 11:30 ` [PATCH 3/5] 9p: revert tsyncfs related changes Aneesh Kumar K.V
2011-03-25 21:20 ` [V9fs-developer] " Venkateswararao Jujjuri
2011-03-27 8:28 ` Aneesh Kumar K. V
2011-03-27 22:24 ` Venkateswararao Jujjuri
2011-03-29 16:05 ` Eric Van Hensbergen
2011-04-15 17:30 ` Aneesh Kumar K.V
2011-03-25 11:30 ` [PATCH 4/5] fs/9p: Fix error reported by coccicheck Aneesh Kumar K.V
2011-03-25 21:27 ` [V9fs-developer] " Venkateswararao Jujjuri
2011-03-25 11:30 ` [PATCH 5/5] 9p: Fix sparse error Aneesh Kumar K.V
2011-03-25 21:26 ` [V9fs-developer] " Venkateswararao Jujjuri
2011-03-25 20:50 ` [V9fs-developer] [PATCH 1/5] fs/9p: Fix revalidate to return correct value Venkateswararao Jujjuri
2011-03-28 20:49 ` Venkateswararao Jujjuri
2011-03-29 4:38 ` Aneesh Kumar K. V
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=4D8CFFDC.7010409@linux.vnet.ibm.com \
--to=jvrao@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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).