Re: [PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-07-01 Thread Matias Bjørling
On 06/30/2016 10:01 PM, J Freyensee wrote: On Wed, 2016-06-29 at 16:51 +0200, Matias Bjørling wrote: From: "Simon A. F. Lund" For a host to access an Open-Channel SSD, it has to know its geometry, so that it writes and reads at the appropriate device bounds. Currently,

Re: [PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-07-01 Thread Matias Bjørling
On 06/30/2016 10:01 PM, J Freyensee wrote: On Wed, 2016-06-29 at 16:51 +0200, Matias Bjørling wrote: From: "Simon A. F. Lund" For a host to access an Open-Channel SSD, it has to know its geometry, so that it writes and reads at the appropriate device bounds. Currently, the geometry

Re: [PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-06-30 Thread J Freyensee
On Wed, 2016-06-29 at 16:51 +0200, Matias Bjørling wrote: > From: "Simon A. F. Lund" > > For a host to access an Open-Channel SSD, it has to know its > geometry, > so that it writes and reads at the appropriate device bounds. > > Currently, the geometry information is kept

Re: [PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-06-30 Thread J Freyensee
On Wed, 2016-06-29 at 16:51 +0200, Matias Bjørling wrote: > From: "Simon A. F. Lund" > > For a host to access an Open-Channel SSD, it has to know its > geometry, > so that it writes and reads at the appropriate device bounds. > > Currently, the geometry information is kept within the kernel,

[PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-06-29 Thread Matias Bjørling
From: "Simon A. F. Lund" For a host to access an Open-Channel SSD, it has to know its geometry, so that it writes and reads at the appropriate device bounds. Currently, the geometry information is kept within the kernel, and not exported to user-space for consumption. This

[PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-06-29 Thread Matias Bjørling
From: "Simon A. F. Lund" For a host to access an Open-Channel SSD, it has to know its geometry, so that it writes and reads at the appropriate device bounds. Currently, the geometry information is kept within the kernel, and not exported to user-space for consumption. This patch exposes the

[PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-06-10 Thread Matias Bjørling
From: "Simon A. F. Lund" For a host to access an Open-Channel SSD, it has to know its geometry, so that it writes and reads at the appropriate device bounds. Currently, the geometry information is kept within the kernel, and not exported to user-space for consumption. This

[PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-06-10 Thread Matias Bjørling
From: "Simon A. F. Lund" For a host to access an Open-Channel SSD, it has to know its geometry, so that it writes and reads at the appropriate device bounds. Currently, the geometry information is kept within the kernel, and not exported to user-space for consumption. This patch exposes the

[RFC PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-06-06 Thread Matias Bjørling
From: Simon Lund For a host to access an Open-Channel SSD, it has to know its geometry, so that it writes and reads at the appropriate device bounds. The geometry information is kept within the kernel, and not exported to user-space for consumption. This patch exposes the

[RFC PATCH 5/6] lightnvm: expose device geometry through sysfs

2016-06-06 Thread Matias Bjørling
From: Simon Lund For a host to access an Open-Channel SSD, it has to know its geometry, so that it writes and reads at the appropriate device bounds. The geometry information is kept within the kernel, and not exported to user-space for consumption. This patch exposes the configuration through