On Tue, Dec 12, 2017 at 01:10:13PM -0500, Mike Snitzer wrote:
> On Mon, Dec 11 2017 at 11:00am -0500,
> Scott Bauer wrote:
>
> OK, but I'm left wondering: why doesn't the user avoid striping across
> the cores?
>
> Do the Intel NVMe drives not provide the ability to present 1 device per
> NVMe c
On Mon, Dec 11 2017 at 11:00am -0500,
Scott Bauer wrote:
> Signed-off-by: Scott Bauer
> ---
> Documentation/device-mapper/dm-unstripe.txt | 82
> +
> 1 file changed, 82 insertions(+)
> create mode 100644 Documentation/device-mapper/dm-unstripe.txt
>
> diff --git a
On Tue, Dec 12, 2017 at 07:45:56AM -0700, Keith Busch wrote:
> Ah, this device's makers call the "stripe" size what should be called
> "chunk".
If this target is to go anywhere, let's try to define it as 'undoing'
the existing dm-stripe target using primary terminology, field names
etc. as close a
On Tue, Dec 12, 2017 at 01:35:13PM +0200, Nikolay Borisov wrote:
> On 11.12.2017 18:00, Scott Bauer wrote:
> > +As an example:
> > +
> > +Intel NVMe drives contain two cores on the physical device.
> > +Each core of the drive has segregated access to its LBA range.
> > +The current
On 11.12.2017 18:00, Scott Bauer wrote:
> Signed-off-by: Scott Bauer
> ---
> Documentation/device-mapper/dm-unstripe.txt | 82
> +
> 1 file changed, 82 insertions(+)
> create mode 100644 Documentation/device-mapper/dm-unstripe.txt
>
> diff --git a/Documentation/de
On Mon, Dec 11, 2017 at 09:00:19AM -0700, Scott Bauer wrote:
> +Example scripts:
> +
> +
> +dmsetup create nvmset1 --table '0 1 dm-unstripe /dev/nvme0n1 1 2 0'
> +dmsetup create nvmset0 --table '0 1 dm-unstripe /dev/nvme0n1 0 2 0'
> +
> +There will now be two mappers:
> +/dev/ma
Signed-off-by: Scott Bauer
---
Documentation/device-mapper/dm-unstripe.txt | 82 +
1 file changed, 82 insertions(+)
create mode 100644 Documentation/device-mapper/dm-unstripe.txt
diff --git a/Documentation/device-mapper/dm-unstripe.txt
b/Documentation/device-mapper/
7 matches
Mail list logo