Re: [PATCH v5 4/5] null_blk: LightNVM support

2015-07-25 Thread Christoph Hellwig
On Thu, Jul 23, 2015 at 12:48:00PM +0200, Matias Bj?rling wrote: > 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

Re: [PATCH v5 4/5] null_blk: LightNVM support

2015-07-25 Thread Christoph Hellwig
On Thu, Jul 23, 2015 at 12:48:00PM +0200, Matias Bj?rling wrote: 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

Re: [PATCH v5 4/5] null_blk: LightNVM support

2015-07-23 Thread Matias Bjørling
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

Re: [PATCH v5 4/5] null_blk: LightNVM support

2015-07-23 Thread Christoph Hellwig
Any reason you're adding this to null_blk instead of having a separate null_nvm driver? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read

Re: [PATCH v5 4/5] null_blk: LightNVM support

2015-07-23 Thread Christoph Hellwig
Any reason you're adding this to null_blk instead of having a separate null_nvm driver? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the

Re: [PATCH v5 4/5] null_blk: LightNVM support

2015-07-23 Thread Matias Bjørling
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

[PATCH v5 4/5] null_blk: LightNVM support

2015-07-22 Thread Matias Bjørling
Initial support for LightNVM. The support can be used to benchmark performance of targets and core implementation. Signed-off-by: Matias Bjørling --- Documentation/block/null_blk.txt | 8 +++ drivers/block/null_blk.c | 138 +-- 2 files changed, 140

[PATCH v5 4/5] null_blk: LightNVM support

2015-07-22 Thread Matias Bjørling
Initial support for LightNVM. The support can be used to benchmark performance of targets and core implementation. Signed-off-by: Matias Bjørling m...@lightnvm.io --- Documentation/block/null_blk.txt | 8 +++ drivers/block/null_blk.c | 138 +-- 2