From: Bart Van Assche <bvanassche@acm.org>
To: device-mapper development <dm-devel@redhat.com>,
Matias Bj??rling <m@bjorling.me>
Cc: snitzer@redhat.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, agk@redhat.com,
Takashi HOSHINO <hoshino@labs.cybozu.co.jp>
Subject: Re: [dm-devel] [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs
Date: Mon, 24 Mar 2014 07:13:15 +0100 [thread overview]
Message-ID: <532FCCFB.7010007@acm.org> (raw)
In-Reply-To: <20140321153749.GA17155@infradead.org>
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.
next prev parent reply other threads:[~2014-03-24 6:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 6:32 [PATCH RFC v1 00/01] dm-lightnvm introduction Matias Bjørling
2014-03-21 6:32 ` [PATCH RFC v1 01/01] dm-lightnvm: An open FTL for open firmware SSDs Matias Bjørling
2014-03-21 15:09 ` Mike Snitzer
2014-03-21 15:26 ` Matias Bjorling
2014-03-21 15:37 ` Christoph Hellwig
2014-03-21 16:24 ` Matias Bjorling
2014-03-25 2:22 ` [dm-devel] " Akira Hayakawa
2014-03-25 3:45 ` Matias Bjorling
2014-03-24 6:13 ` Bart Van Assche [this message]
2014-03-25 3:30 ` Matias Bjorling
2014-03-25 11:38 ` Takashi HOSHINO
2014-03-21 9:06 ` [dm-devel] [PATCH RFC v1 00/01] dm-lightnvm introduction Joe Thornber
2014-03-21 15:22 ` Matias Bjorling
2014-03-25 3:08 ` David Lang
2014-03-25 3:56 ` Matias Bjorling
2014-03-25 17:23 ` Richard Weinberger
2014-03-21 15:32 ` Richard Weinberger
2014-03-21 16:42 ` Matias Bjorling
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=532FCCFB.7010007@acm.org \
--to=bvanassche@acm.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hoshino@labs.cybozu.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m@bjorling.me \
--cc=snitzer@redhat.com \
/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