From: Kent Overstreet <kmo@daterainc.com>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Rolf Fokkens <rolf@rolffokkens.nl>, Slava Pestov <sp@datera.io>,
"Stephen R. van den Berg" <srb@cuci.nl>,
linux-bcache@vger.kernel.org
Subject: Re: 3.18.1 + latest bcache-dev
Date: Wed, 7 Jan 2015 18:30:54 -0800 [thread overview]
Message-ID: <20150108023054.GB1263@kmo-pixel> (raw)
In-Reply-To: <alpine.DEB.2.02.1501071214210.19734@ware.dreamhost.com>
On Wed, Jan 07, 2015 at 12:17:19PM -0800, Eric Wheeler wrote:
> On Tue, 6 Jan 2015, Rolf Fokkens wrote:
>
> > On 01/05/2015 08:47 AM, Slava Pestov wrote:
> > > The plan is to incrementally backport bug fixes and optimizations from
> > > bcache-dev to upstream for the foreseeable future.
> > As an ethousiastic bcache user myself I would be very happy if there's a
> > transition plan! :-)
>
> Would it make sense to call this bcache2 and merge both into the linux
> tree once bcache2 is stable enough for broader testing?
Yeah that might be what happens.
> To the extent possible, you could reuse common code paths and simplify the
> backporting of bug fixes into the existing stable branch.
Code reuse is problematic because struct bkey itself changes, a lot of the code
that's factored out as a library now depends on the specific layout of struct
bkey :/
Gonna try and backport as much as possible that doesn't require changing the on
disk format when I have time, though.
next prev parent reply other threads:[~2015-01-08 2:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 2:35 3.18.1 + latest bcache-dev Stephen R. van den Berg
2014-12-29 4:05 ` Slava Pestov
2015-01-03 16:40 ` Rolf Fokkens
2015-01-04 0:46 ` Kent Overstreet
2015-01-04 14:11 ` Rolf Fokkens
2015-01-05 7:47 ` Slava Pestov
2015-01-06 22:18 ` Rolf Fokkens
2015-01-06 22:47 ` Slava Pestov
2015-01-07 1:48 ` Kent Overstreet
2015-01-07 17:41 ` Jianjian Huo
2015-01-08 2:29 ` Kent Overstreet
2015-01-07 20:17 ` Eric Wheeler
2015-01-08 2:30 ` Kent Overstreet [this message]
2015-01-08 19:47 ` Rolf Fokkens
2015-01-05 8:49 ` Stephen R. van den Berg
2015-01-05 11:06 ` Kent Overstreet
2015-01-06 9:16 ` Stephen R. van den Berg
2015-01-06 11:10 ` Kent Overstreet
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=20150108023054.GB1263@kmo-pixel \
--to=kmo@daterainc.com \
--cc=bcache@lists.ewheeler.net \
--cc=linux-bcache@vger.kernel.org \
--cc=rolf@rolffokkens.nl \
--cc=sp@datera.io \
--cc=srb@cuci.nl \
/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