All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sahitya Tummala <stummala@codeaurora.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>, linux-ext4@vger.kernel.org
Subject: Re: fsync_mode mount option for ext4
Date: Tue, 28 May 2019 09:18:30 +0530	[thread overview]
Message-ID: <20190528034830.GH10043@codeaurora.org> (raw)
In-Reply-To: <20190528034007.GA19149@mit.edu>

Hi Ted,

On Mon, May 27, 2019 at 11:40:07PM -0400, Theodore Ts'o wrote:
> On Tue, May 28, 2019 at 08:52:57AM +0530, Sahitya Tummala wrote:
> > Hi Ted, Andreas,
> > 
> > Do you think this mount option "fsync_mode=nobarrier"
> > can be added for EXT4 as well like in F2FS? Please
> > share your thoughts on this.
> > 
> > https://lore.kernel.org/patchwork/patch/908934/
> 
> Ext4 already has the nobarrier mount option.
> 

Yes, but fsync_mode=nobarrier is little different than
a general nobarrier option. The fsync_mode=nobarrier is
only controlling the flush policy for fsync() path, unlike
the nobarrier mount option which is applicable at all
places in the filesystem.

Thanks,

> Cheers,
> 
>      	     	     	       	     - Ted

-- 
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2019-05-28  3:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28  3:22 fsync_mode mount option for ext4 Sahitya Tummala
2019-05-28  3:40 ` Theodore Ts'o
2019-05-28  3:48   ` Sahitya Tummala [this message]
2019-05-28 13:13     ` Theodore Ts'o
2019-05-29  4:07       ` Sahitya Tummala
2019-05-29  5:23         ` Theodore Ts'o
2019-05-29  6:56           ` Christoph Hellwig
2019-05-29 10:48           ` Sahitya Tummala
2019-05-29 15:13             ` Theodore Ts'o

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=20190528034830.GH10043@codeaurora.org \
    --to=stummala@codeaurora.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.