From: Ted Ts'o <tytso@mit.edu> To: Lawrence Greenfield <leg@google.com> Cc: Dave Chinner <david@fromorbit.com>, Josef Bacik <josef@redhat.com>, linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com, joel.becker@oracle.com, cmm@us.ibm.com, cluster-devel@redhat.com Subject: Re: [PATCH 1/6] fs: add hole punching to fallocate Date: Tue, 11 Jan 2011 16:30:07 -0500 [thread overview] Message-ID: <20110111213007.GF2917@thunk.org> (raw) In-Reply-To: <AANLkTimwmJ_ZoE9oAuA1WGhCgK585jDznqnc6k0=9Ntb@mail.gmail.com> On Tue, Jan 11, 2011 at 04:13:42PM -0500, Lawrence Greenfield wrote: > > IOWs, all they want to do is avoid the unwritten extent conversion > > overhead. Time has shown that a bad security/performance tradeoff > > decision was made 13 years ago in XFS, so I see little reason to > > repeat it for ext4 today.... I suspect things may have changed somewhat; both in terms of requirements and nature of cluter file systems, and the performance of various storage systems (including PCIe-attached flash devices). > I'd make use of FALLOC_FL_EXPOSE_OLD_DATA. It's not the CPU overhead > of extent conversion. It's that extent conversion causes more metadata > operations than what you'd have otherwise, which means systems that > want to use O_DIRECT and make sure the data doesn't go away either > have to write O_DIRECT|O_DSYNC or need to call fdatasync(). > > cluster file system implementor, One possibility might be to make it an optional feature which is only enabled via a mount option. That way someone would have to explicit ask for this feature two ways (via a new flag to fallocate) and a mount option. It might not make sense for XFS, but for people who are using ext4 as the local storage file system back-end, and are doing all sorts of things to get the best performance, including disabling the journal, I suspect it really would make sense. So it could always be an optional-to-implement flag, that not all file systems should feel obliged to implement. - Ted
WARNING: multiple messages have this Message-ID (diff)
From: "Ted Ts'o" <tytso@mit.edu> To: Lawrence Greenfield <leg@google.com> Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com, cluster-devel@redhat.com, cmm@us.ibm.com, Josef Bacik <josef@redhat.com>, joel.becker@oracle.com, linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org Subject: Re: [PATCH 1/6] fs: add hole punching to fallocate Date: Tue, 11 Jan 2011 16:30:07 -0500 [thread overview] Message-ID: <20110111213007.GF2917@thunk.org> (raw) In-Reply-To: <AANLkTimwmJ_ZoE9oAuA1WGhCgK585jDznqnc6k0=9Ntb@mail.gmail.com> On Tue, Jan 11, 2011 at 04:13:42PM -0500, Lawrence Greenfield wrote: > > IOWs, all they want to do is avoid the unwritten extent conversion > > overhead. Time has shown that a bad security/performance tradeoff > > decision was made 13 years ago in XFS, so I see little reason to > > repeat it for ext4 today.... I suspect things may have changed somewhat; both in terms of requirements and nature of cluter file systems, and the performance of various storage systems (including PCIe-attached flash devices). > I'd make use of FALLOC_FL_EXPOSE_OLD_DATA. It's not the CPU overhead > of extent conversion. It's that extent conversion causes more metadata > operations than what you'd have otherwise, which means systems that > want to use O_DIRECT and make sure the data doesn't go away either > have to write O_DIRECT|O_DSYNC or need to call fdatasync(). > > cluster file system implementor, One possibility might be to make it an optional feature which is only enabled via a mount option. That way someone would have to explicit ask for this feature two ways (via a new flag to fallocate) and a mount option. It might not make sense for XFS, but for people who are using ext4 as the local storage file system back-end, and are doing all sorts of things to get the best performance, including disabling the journal, I suspect it really would make sense. So it could always be an optional-to-implement flag, that not all file systems should feel obliged to implement. - Ted _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-11 21:30 UTC|newest] Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-08 20:32 [PATCH 1/6] fs: add hole punching to fallocate Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-08 20:32 ` [PATCH 2/6] XFS: handle hole punching via fallocate properly Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-09 1:22 ` Dave Chinner 2010-11-09 1:22 ` Dave Chinner 2010-11-09 2:05 ` Josef Bacik 2010-11-09 2:05 ` Josef Bacik 2010-11-09 4:21 ` Dave Chinner 2010-11-09 4:21 ` Dave Chinner 2010-11-08 20:32 ` [PATCH 3/6] Ocfs2: " Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-08 20:32 ` [PATCH 4/6] Ext4: fail if we try to use hole punch Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-08 20:32 ` [PATCH 5/6] Btrfs: " Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-09 10:05 ` Will Newton 2010-11-09 10:05 ` Will Newton 2010-11-09 10:05 ` Will Newton 2010-11-09 10:05 ` Will Newton 2010-11-09 12:53 ` Josef Bacik 2010-11-09 12:53 ` Josef Bacik 2010-11-09 12:53 ` Josef Bacik 2010-11-09 12:53 ` Josef Bacik 2010-11-08 20:32 ` [PATCH 6/6] Gfs2: " Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-08 20:32 ` Josef Bacik 2010-11-09 1:12 ` [PATCH 1/6] fs: add hole punching to fallocate Dave Chinner 2010-11-09 1:12 ` Dave Chinner 2010-11-09 2:10 ` Josef Bacik 2010-11-09 2:10 ` Josef Bacik 2010-11-09 3:30 ` Ted Ts'o 2010-11-09 3:30 ` Ted Ts'o 2010-11-09 4:42 ` Dave Chinner 2010-11-09 4:42 ` Dave Chinner 2010-11-09 4:42 ` Dave Chinner 2010-11-09 21:41 ` Ted Ts'o 2010-11-09 21:41 ` Ted Ts'o 2010-11-09 21:53 ` Jan Kara 2010-11-09 21:53 ` [Cluster-devel] " Jan Kara 2010-11-09 21:53 ` Jan Kara 2010-11-09 23:40 ` Dave Chinner 2010-11-09 23:40 ` Dave Chinner 2010-11-09 23:40 ` Dave Chinner 2010-11-09 23:40 ` Dave Chinner 2011-01-11 21:13 ` Lawrence Greenfield 2011-01-11 21:13 ` Lawrence Greenfield 2011-01-11 21:13 ` Lawrence Greenfield 2011-01-11 21:13 ` Lawrence Greenfield 2011-01-11 21:30 ` Ted Ts'o [this message] 2011-01-11 21:30 ` Ted Ts'o 2011-01-12 11:48 ` Dave Chinner 2011-01-12 11:48 ` Dave Chinner 2011-01-12 11:48 ` Dave Chinner 2011-01-12 11:48 ` Dave Chinner 2011-01-12 12:44 ` Dave Chinner 2011-01-12 12:44 ` Dave Chinner 2011-01-28 18:13 ` Ric Wheeler 2011-01-28 18:13 ` Ric Wheeler 2010-11-09 20:51 ` Josef Bacik 2010-11-09 20:51 ` Josef Bacik 2010-11-15 17:05 Hole Punching V2 Josef Bacik 2010-11-15 17:05 ` [PATCH 1/6] fs: add hole punching to fallocate Josef Bacik 2010-11-15 17:05 ` Josef Bacik 2010-11-15 17:05 ` Josef Bacik 2010-11-16 11:16 ` Jan Kara 2010-11-16 11:16 ` Jan Kara 2010-11-16 11:43 ` Jan Kara 2010-11-16 11:43 ` Jan Kara 2010-11-16 12:52 ` Josef Bacik 2010-11-16 12:52 ` Josef Bacik 2010-11-16 13:14 ` Jan Kara 2010-11-16 13:14 ` Jan Kara 2010-11-17 0:22 ` Andreas Dilger 2010-11-17 0:22 ` Andreas Dilger 2010-11-17 2:11 ` Dave Chinner 2010-11-17 2:11 ` Dave Chinner 2010-11-17 2:28 ` Josef Bacik 2010-11-17 2:28 ` Josef Bacik 2010-11-17 2:34 ` Josef Bacik 2010-11-17 2:34 ` Josef Bacik 2010-11-17 9:30 ` Andreas Dilger 2010-11-17 9:30 ` Andreas Dilger 2010-11-17 9:19 ` Andreas Dilger 2010-11-17 9:19 ` Andreas Dilger 2010-11-16 12:53 ` Josef Bacik 2010-11-16 12:53 ` Josef Bacik 2010-11-18 1:46 Hole Punching V3 Josef Bacik 2010-11-18 1:46 ` [PATCH 1/6] fs: add hole punching to fallocate Josef Bacik 2010-11-18 1:46 ` Josef Bacik 2010-11-18 1:46 ` Josef Bacik 2010-11-18 23:43 ` Jan Kara 2010-11-18 23:43 ` Jan Kara
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=20110111213007.GF2917@thunk.org \ --to=tytso@mit.edu \ --cc=cluster-devel@redhat.com \ --cc=cmm@us.ibm.com \ --cc=david@fromorbit.com \ --cc=joel.becker@oracle.com \ --cc=josef@redhat.com \ --cc=leg@google.com \ --cc=linux-btrfs@vger.kernel.org \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=xfs@oss.sgi.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: linkBe 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.