From: Emmanuel Florac <eflorac@intellique.com>
To: linux-bcache@vger.kernel.org
Subject: Why bcachefs?
Date: Tue, 18 Aug 2015 13:29:21 +0200 [thread overview]
Message-ID: <20150818132921.7ef7db8b@harpe.intellique.com> (raw)
After toying a bit with it, I'm wondering: why bcachefs? I understand
that integrating the filesystem with the cache layer probably makes the
job easier but overall ... we already have several excellent
filesystems; developing a reliable filesystem is DAMN HARD; building a
feature-complete FS is CRAZY HARD (see btrfs); because FTL sucks anyway
and we'd rather wait for ways to move ahead of it...
So Kent, please, tell us, why? :)
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
reply other threads:[~2015-08-18 11:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150818132921.7ef7db8b@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=linux-bcache@vger.kernel.org \
/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).