From: Sahitya Tummala <stummala@codeaurora.org>
To: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org
Cc: stummala@codeaurora.org
Subject: fsync_mode mount option for ext4
Date: Tue, 28 May 2019 08:52:57 +0530 [thread overview]
Message-ID: <20190528032257.GF10043@codeaurora.org> (raw)
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/
Thanks,
Sahitya.
--
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2019-05-28 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 3:22 Sahitya Tummala [this message]
2019-05-28 3:40 ` fsync_mode mount option for ext4 Theodore Ts'o
2019-05-28 3:48 ` Sahitya Tummala
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=20190528032257.GF10043@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 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).