From: Matthew Wilcox <matthew@wil.cx>
To: Andreas Dilger <adilger@whamcloud.com>
Cc: Zach Brown <zab@zabbo.net>,
"faibish_sorin@emc.com" <faibish_sorin@emc.com>,
"sarah.jelinek@intel.com" <sarah.jelinek@intel.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: Inode metadata and file data syncing
Date: Thu, 19 Jul 2012 12:08:44 -0600 [thread overview]
Message-ID: <20120719180843.GA31693@parisc-linux.org> (raw)
In-Reply-To: <5D277944-1E64-4B12-96B5-EF1A3C857371@whamcloud.com>
On Thu, Jul 19, 2012 at 10:11:18AM -0700, Andreas Dilger wrote:
> Sure, I totally agree. I just wanted to head off any efforts that are just duplicating btrfs or cachefs or whatever for very little total benefit.
I can assure you there's nothing out there like this :-)
> It's also worthwhile to ask that question early on, before there is a large vested interest in the new filesystem, rather than months/years later when the time and effort is already sunk into the other project and not some existing project.
My initial commit to this project was July 2009. It takes a long time
to get from "wouldn't it be crazy if ..." to production quality hardware.
And, of course, there are never false turns along that path!
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
prev parent reply other threads:[~2012-07-19 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 16:53 Inode metadata and file data syncing Jelinek, Sarah
2012-07-18 17:21 ` Josef Bacik
2012-07-18 17:52 ` Jelinek, Sarah
2012-07-19 1:48 ` Andreas Dilger
2012-07-19 12:44 ` Jelinek, Sarah
2012-07-19 13:12 ` faibish_sorin
2012-07-19 13:18 ` Jelinek, Sarah
2012-07-19 13:50 ` faibish_sorin
2012-07-19 16:49 ` Zach Brown
2012-07-19 17:11 ` Andreas Dilger
2012-07-19 18:08 ` Matthew Wilcox [this message]
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=20120719180843.GA31693@parisc-linux.org \
--to=matthew@wil.cx \
--cc=adilger@whamcloud.com \
--cc=faibish_sorin@emc.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sarah.jelinek@intel.com \
--cc=zab@zabbo.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).