ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/2] ocfs2: Flush drive's caches on fdatasync
Date: Fri, 30 Jul 2010 16:47:04 +0200	[thread overview]
Message-ID: <20100730144704.GA3273@quack.suse.cz> (raw)
In-Reply-To: <4C5233CB.5000600@oracle.com>

On Fri 30-07-10 10:07:07, Tao Ma wrote:
> Hi Jan,
> 
> On 07/29/2010 08:00 PM, Jan Kara wrote:
> >We have to issue a cache flush during fdatasync even if inode doesn't have
> >I_DIRTY_DATASYNC set because we still have to get written *data* to disk to
> >observe fdatasync() guarantees.
> I am fine with the patch from the code's perspective.
> 
> But I just noticed the discussion in fsdevel with the subject
> "relaxed barrier semantics", so with barrier there will be a massive
> slowdowns according to Christoph. And as ocfs2 is mainly used with
> some SAN, I guess in most cases the storage will have a battery
> backed cache, so we may not need this?
  Yes, barriers are rather heavy operation and battery backed SANs don't
need them. In this regard, you are right my patch forgot to check the
OCFS2_MOUNT_BARRIER option. But when the option is set, we must send the
barrier. Otherwise we risk user's data on crash... Below is a fixed version
of the patch.

									Honza
---
From 61c46d394bdc9915554b499f7c3154bde13f3ee5 Mon Sep 17 00:00:00 2001
From: Jan Kara <jack@suse.cz>
Date: Thu, 29 Jul 2010 13:32:19 +0200
Subject: [PATCH 1/2] ocfs2: Flush drive's caches on fdatasync

We have to issue a cache flush during fdatasync even if inode doesn't have
I_DIRTY_DATASYNC set because we still have to get written *data* to disk to
observe fdatasync() guarantees.

Signed-off-by: Jan Kara <jack@suse.cz>
---
 fs/ocfs2/file.c |   11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c
index 2b10b36..3ed8efd 100644
--- a/fs/ocfs2/file.c
+++ b/fs/ocfs2/file.c
@@ -36,6 +36,7 @@
 #include <linux/writeback.h>
 #include <linux/falloc.h>
 #include <linux/quotaops.h>
+#include <linux/blkdev.h>
 
 #define MLOG_MASK_PREFIX ML_INODE
 #include <cluster/masklog.h>
@@ -190,8 +191,16 @@ static int ocfs2_sync_file(struct file *file, int datasync)
 	if (err)
 		goto bail;
 
-	if (datasync && !(inode->i_state & I_DIRTY_DATASYNC))
+	if (datasync && !(inode->i_state & I_DIRTY_DATASYNC)) {
+		/*
+		 * We still have to flush drive's caches to get data to the
+		 * platter
+		 */
+		if (osb->s_mount_opt & OCFS2_MOUNT_BARRIER)
+			blkdev_issue_flush(inode->i_sb->s_bdev, GFP_KERNEL,
+					   NULL, BLKDEV_IFL_WAIT);
 		goto bail;
+	}
 
 	journal = osb->journal->j_journal;
 	err = jbd2_journal_force_commit(journal);
-- 
1.6.4.2

  parent reply	other threads:[~2010-07-30 14:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 12:00 [Ocfs2-devel] [PATCH 1/2] ocfs2: Flush drive's caches on fdatasync Jan Kara
2010-07-29 12:00 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: Remove ocfs2_sync_inode() Jan Kara
2010-07-30  2:07 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: Flush drive's caches on fdatasync Tao Ma
2010-07-30  2:12   ` Sunil Mushran
2010-07-30 14:47   ` Jan Kara [this message]
2010-08-02  5:47     ` Tao Ma

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=20100730144704.GA3273@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=ocfs2-devel@oss.oracle.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).