[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <532FCCFB.7010007@acm.org>
Date: Mon, 24 Mar 2014 07:13:15 +0100
From: Bart Van Assche <bvanassche@....org>
To: device-mapper development <dm-devel@...hat.com>,
Matias Bj??rling <m@...rling.me>
CC: snitzer@...hat.com, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, agk@...hat.com,
Takashi HOSHINO <hoshino@...s.cybozu.co.jp>
Subject: Re: [dm-devel] [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for
open firmware SSDs
On 03/21/14 16:37, Christoph Hellwig wrote:
> Just curious: why do you think implementing this as a block remapper
> inside device mapper is a better idea than as a blk-mq driver?
>
> At the request layer you already get a lot of infrastructure for all the
> queueing infrastructure for free, as well as all kinds of other helpers.
> And the driver never remaps bios anyway but always submits new ones as
> far as I can tell.
>
> Does it even make sense to expose the underlying devices as block
> devices? It surely would help to send this together with a driver
> that you plan to use it on top of.
There might be some overlap between the functionality available in the
lightnvm driver and the WalB driver announced last year. That last
driver might have a wider user base and hence may have received more
testing. See also http://thread.gmane.org/gmane.linux.file-systems/75124.
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists