From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vivek Goyal Subject: Re: [Bcache v13 00/16] Date: Thu, 10 May 2012 09:54:31 -0400 Message-ID: <20120510135431.GC23768@redhat.com> References: Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Kent Overstreet Cc: linux-bcache@vger.kernel.org, agk@redhat.com, tejun@google.com, linux-kernel@vger.kernel.org, dm-devel@redhat.com List-Id: linux-bcache@vger.kernel.org On Wed, May 09, 2012 at 11:07:29PM -0400, Kent Overstreet wrote: > bcache: a cache for arbitrary block devices using an SSD. > > Short overview: > Bcache does both writethrough and writeback caching. It presents itself as a > new block device, a bit like say md. You can cache an arbitrary number of > block devices with a single cache device, and attach and detach things at > runtime - it's quite flexible. So it is still not a device mapper target. I somehow had the impression that consensus at LSF was to convert it into a device mapper target. Thanks Vivek