From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: James Bottomley
<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org,
snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
neilb-l3A5Bk7waGM@public.gmane.org
Subject: Re: Bcache v. whatever
Date: Tue, 15 Jan 2013 12:59:12 -0800 [thread overview]
Message-ID: <20130115205912.GA26407@google.com> (raw)
In-Reply-To: <1358241656.2383.2.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
On Tue, Jan 15, 2013 at 09:20:56AM +0000, James Bottomley wrote:
> On Mon, 2013-01-14 at 14:32 -0800, Kent Overstreet wrote:
> > Bcache: a block layer SSD cache
> >
> > Does writethrough and writeback, handles unclean shutdown, and has
> > various other nifty features. See the wiki and the documentation for
> > more:
> >
> > http://bcache.evilpiepirate.org
> >
> > Over the Christmas break I finally got the tree into a self contained
> > state that ought to be suitable for merging; this tree is fairly close
> > to the previous stable tree that people have been running on production
> > servers for awhile (and that I've been running on this workstation),
> >
> > So, I think this is ready for mainline and I'd like to get it in. I
> > should've tried to push it ages ago, but I was hoping to get in various
> > block layer cleanups first; I finally deided to work around them in the
> > meantime since I haven't had time to finish the block layer stuff.
> >
> > Not everything has been addressed since I last posted for review
> > feedback - notably the closure code was controversial and for now I've
> > just moved that into drivers/block/bcache (though I've been refactoring
> > stuff to make it less asynchronous lately; most of that work is in the
> > testing/dev branches). The bigger issue IMO is the userspace interface -
> > I'd like to finish the md integration so it doesn't need userspace stuff
> > for probing/bootup. So, I'd be fine with it going into staging if that's
> > the consensus, but it's stable tested code.
> >
> > The code is available at
> > http://evilpiepirate.org/git/linux-bcache.git bcache-for-upstream
> >
> > This latest branch is on top of v3.8-rc3:
>
> The guy to merge this is the maintainer in that layer, which is Alasdair
> Kergon. I know you've been sending patches to the dm-devel list, what's
> the reason you didn't include him in the cc list? Is there some type of
> political problem in dm? From reading the list, it looks like your
> patches are being tested and progressing, so what am I missing?
That was merely an oversight - but, bcache is currently just another
block device, it doesn't plug into dm or md. There was some md
integration work started, and that's the one I'm more inclined to work
on personally (if and when I find the time).
So I'm not sure why it'd go in via dm, it seems to me it'd make just as
much sense for it to go in via Neil Brown's tree. Unless there's
something I'm missing?
WARNING: multiple messages have this Message-ID (diff)
From: Kent Overstreet <koverstreet@google.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org,
akpm@linux-foundation.org, tj@kernel.org, axboe@kernel.dk,
snitzer@redhat.com, agk@redhat.com, neilb@suse.de
Subject: Re: Bcache v. whatever
Date: Tue, 15 Jan 2013 12:59:12 -0800 [thread overview]
Message-ID: <20130115205912.GA26407@google.com> (raw)
In-Reply-To: <1358241656.2383.2.camel@dabdike.int.hansenpartnership.com>
On Tue, Jan 15, 2013 at 09:20:56AM +0000, James Bottomley wrote:
> On Mon, 2013-01-14 at 14:32 -0800, Kent Overstreet wrote:
> > Bcache: a block layer SSD cache
> >
> > Does writethrough and writeback, handles unclean shutdown, and has
> > various other nifty features. See the wiki and the documentation for
> > more:
> >
> > http://bcache.evilpiepirate.org
> >
> > Over the Christmas break I finally got the tree into a self contained
> > state that ought to be suitable for merging; this tree is fairly close
> > to the previous stable tree that people have been running on production
> > servers for awhile (and that I've been running on this workstation),
> >
> > So, I think this is ready for mainline and I'd like to get it in. I
> > should've tried to push it ages ago, but I was hoping to get in various
> > block layer cleanups first; I finally deided to work around them in the
> > meantime since I haven't had time to finish the block layer stuff.
> >
> > Not everything has been addressed since I last posted for review
> > feedback - notably the closure code was controversial and for now I've
> > just moved that into drivers/block/bcache (though I've been refactoring
> > stuff to make it less asynchronous lately; most of that work is in the
> > testing/dev branches). The bigger issue IMO is the userspace interface -
> > I'd like to finish the md integration so it doesn't need userspace stuff
> > for probing/bootup. So, I'd be fine with it going into staging if that's
> > the consensus, but it's stable tested code.
> >
> > The code is available at
> > http://evilpiepirate.org/git/linux-bcache.git bcache-for-upstream
> >
> > This latest branch is on top of v3.8-rc3:
>
> The guy to merge this is the maintainer in that layer, which is Alasdair
> Kergon. I know you've been sending patches to the dm-devel list, what's
> the reason you didn't include him in the cc list? Is there some type of
> political problem in dm? From reading the list, it looks like your
> patches are being tested and progressing, so what am I missing?
That was merely an oversight - but, bcache is currently just another
block device, it doesn't plug into dm or md. There was some md
integration work started, and that's the one I'm more inclined to work
on personally (if and when I find the time).
So I'm not sure why it'd go in via dm, it seems to me it'd make just as
much sense for it to go in via Neil Brown's tree. Unless there's
something I'm missing?
next prev parent reply other threads:[~2013-01-15 20:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 22:32 Bcache v. whatever Kent Overstreet
2013-01-14 22:32 ` Kent Overstreet
2013-01-15 1:49 ` Greg KH
[not found] ` <20130115014931.GA19373-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-01-15 21:18 ` Kent Overstreet
2013-01-15 21:18 ` Kent Overstreet
2013-01-15 22:50 ` Greg KH
[not found] ` <20130114223202.GV26407-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-01-15 9:20 ` James Bottomley
2013-01-15 9:20 ` James Bottomley
[not found] ` <1358241656.2383.2.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-01-15 20:59 ` Kent Overstreet [this message]
2013-01-15 20:59 ` Kent Overstreet
2013-01-15 23:15 ` James Bottomley
2013-01-15 23:33 ` Kent Overstreet
[not found] ` <20130115233347.GD26407-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-01-16 1:29 ` Alasdair G Kergon
2013-01-16 1:29 ` Alasdair G Kergon
[not found] ` <20130116012914.GA27245-FDJ95KluN3Z0klwcnFlA1dvLeJWuRmrY@public.gmane.org>
2013-01-17 23:43 ` Mike Snitzer
2013-01-17 23:43 ` Mike Snitzer
2013-01-15 21:25 ` [PATCH 1/4] Revert "rw_semaphore: remove up/down_read_non_owner" Kent Overstreet
2013-01-15 21:25 ` Kent Overstreet
2013-04-25 23:17 ` Bcache v. whatever Andrew Morton
2013-04-25 23:17 ` Andrew Morton
[not found] ` <20130425161704.3f0fc3b6af55cf75acbc9d9e-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2013-04-26 19:46 ` Kent Overstreet
2013-04-26 19:46 ` Kent Overstreet
[not found] ` <20130426194642.GC9931-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-04-26 20:24 ` Andrew Morton
2013-04-26 20:24 ` Andrew Morton
[not found] ` <20130426132438.4e48e0688fc3c3c298e71d7e-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2013-04-26 20:54 ` Kent Overstreet
2013-04-26 20:54 ` Kent Overstreet
2013-01-15 21:25 ` [PATCH 2/4] Export get_random_int() Kent Overstreet
2013-01-15 21:25 ` [PATCH 3/4] Export blk_fill_rwbs() Kent Overstreet
[not found] ` <1358285142-10576-3-git-send-email-koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-02-01 3:48 ` Steven Rostedt
2013-02-01 3:48 ` Steven Rostedt
[not found] ` <1359690521.5642.10.camel-f9ZlEuEWxVcJvu8Pb33WZ0EMvNT87kid@public.gmane.org>
2013-02-01 3:57 ` Li Zefan
2013-02-01 3:57 ` Li Zefan
[not found] ` <510B3D2A.3040007-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-02-01 4:06 ` Steven Rostedt
2013-02-01 4:06 ` Steven Rostedt
2013-01-15 21:25 ` [PATCH 4/4] Export __lockdep_no_validate__ Kent Overstreet
[not found] <koverstreet@google.com>
2013-01-15 6:59 ` Bcache v. whatever Dr. Greg Wettstein
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=20130115205912.GA26407@google.com \
--to=koverstreet-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
--cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=neilb-l3A5Bk7waGM@public.gmane.org \
--cc=snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.