From: Kent Overstreet <kent.overstreet@gmail.com>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: linux-bcache@vger.kernel.org
Subject: Re: bcachefs: can bcachefs export block devices?
Date: Wed, 3 Aug 2016 22:04:05 -0800 [thread overview]
Message-ID: <20160804060405.GA8042@kmo-pixel> (raw)
In-Reply-To: <alpine.LRH.2.11.1608031727480.10662@mail.ewheeler.net>
On Wed, Aug 03, 2016 at 05:30:02PM -0700, Eric Wheeler wrote:
> Hey Kent,
>
> I noticed that blockdev.c got an overhaul in bcache-dev recently. Getting
> closer to blockdev export from bcachefs?
No, not really. I've actually hardly touched that stuff - to the extent that I
have I've just been fixing a few random bugs here and there to get the old style
bcache functionality closer to working again.
> Actually it looks like you've been pretty busy on that branch in general.
>
> What's new?
Oh, random stuff. I've been posting some on patreon lately:
https://www.patreon.com/bcachefs
(And yes, I do need money if anyone would be willing to chip in).
The main user visible thing is compression is finally useful - I finally
finished the disk accounting stuff so that enabling compression actually lets
you store more data on a fs.
Besides that, it's mainly been bug fixing and internal refactoring working
towards snapshots. I'm gonna write something up about the plan for snapshots
soon.
prev parent reply other threads:[~2016-08-04 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 21:47 bcachefs: can bcachefs export block devices? Eric Wheeler
2016-05-25 22:51 ` Kent Overstreet
2016-05-28 2:45 ` Eric Wheeler
2016-08-04 6:08 ` Kent Overstreet
2016-08-04 23:46 ` Eric Wheeler
2016-08-06 4:34 ` Kent Overstreet
2017-02-09 22:17 ` Eric Wheeler
2017-02-09 22:41 ` Martin Raiber
2016-08-04 0:30 ` Eric Wheeler
2016-08-04 6:04 ` Kent Overstreet [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=20160804060405.GA8042@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=bcache@lists.ewheeler.net \
--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 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.