From: "Matias Bjørling" <mb@lightnvm.io>
To: Christoph Hellwig <hch@infradead.org>
Cc: axboe@fb.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
Stephen.Bates@pmcs.com, keith.busch@intel.com
Subject: Re: [PATCH v5 4/5] null_blk: LightNVM support
Date: Thu, 23 Jul 2015 12:48:00 +0200 [thread overview]
Message-ID: <55B0C660.8010509@lightnvm.io> (raw)
In-Reply-To: <20150723095351.GB26420@infradead.org>
On 07/23/2015 11:53 AM, Christoph Hellwig wrote:
> Any reason you're adding this to null_blk instead of having a separate
> null_nvm driver?
>
Only reason was to not duplicate the I/O submission/completion flow.
With the simple code at the moment, it is little to add. However, if
someone decides to put backing store, simulation, etc. into it, then it
should properly go into another module.
Do you want me to move it into a new driver for this patchset?
WARNING: multiple messages have this Message-ID (diff)
From: mb@lightnvm.io (Matias Bjørling)
Subject: [PATCH v5 4/5] null_blk: LightNVM support
Date: Thu, 23 Jul 2015 12:48:00 +0200 [thread overview]
Message-ID: <55B0C660.8010509@lightnvm.io> (raw)
In-Reply-To: <20150723095351.GB26420@infradead.org>
On 07/23/2015 11:53 AM, Christoph Hellwig wrote:
> Any reason you're adding this to null_blk instead of having a separate
> null_nvm driver?
>
Only reason was to not duplicate the I/O submission/completion flow.
With the simple code at the moment, it is little to add. However, if
someone decides to put backing store, simulation, etc. into it, then it
should properly go into another module.
Do you want me to move it into a new driver for this patchset?
next prev parent reply other threads:[~2015-07-23 10:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 17:50 [PATCH v5 0/5] Support for Open-Channel SSDs Matias Bjørling
2015-07-22 17:50 ` Matias Bjørling
2015-07-22 17:51 ` [PATCH v5 1/5] lightnvm: " Matias Bjørling
2015-07-22 17:51 ` Matias Bjørling
2015-07-22 17:51 ` Matias Bjørling
2015-07-23 9:53 ` Christoph Hellwig
2015-07-23 9:53 ` Christoph Hellwig
2015-07-23 10:38 ` Matias Bjørling
2015-07-23 10:38 ` Matias Bjørling
2015-07-22 17:51 ` [PATCH v5 2/5] rrpc: Hybrid Open-Channel SSD RRPC target Matias Bjørling
2015-07-22 17:51 ` Matias Bjørling
2015-07-22 17:51 ` [PATCH v5 3/5] bm_hb: Hybrid Open-Channel SSD block manager Matias Bjørling
2015-07-22 17:51 ` Matias Bjørling
2015-07-22 17:51 ` [PATCH v5 4/5] null_blk: LightNVM support Matias Bjørling
2015-07-22 17:51 ` Matias Bjørling
2015-07-23 9:53 ` Christoph Hellwig
2015-07-23 9:53 ` Christoph Hellwig
2015-07-23 10:48 ` Matias Bjørling [this message]
2015-07-23 10:48 ` Matias Bjørling
2015-07-25 6:25 ` Christoph Hellwig
2015-07-25 6:25 ` Christoph Hellwig
2015-07-22 17:51 ` [PATCH v5 5/5] nvme: " Matias Bjørling
2015-07-22 17:51 ` Matias Bjørling
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=55B0C660.8010509@lightnvm.io \
--to=mb@lightnvm.io \
--cc=Stephen.Bates@pmcs.com \
--cc=axboe@fb.com \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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.