diff options
author | Javier González <jg@lightnvm.io> | 2016-11-28 22:39:05 +0100 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2016-11-29 12:12:51 -0700 |
commit | 8176117b82e49e043d045f214ba7a892fba6b827 (patch) | |
tree | 313d9fbd1d0df7ae9aac03b6f84d01159d3025bf /drivers/nvme | |
parent | de93434fcf74d41754a48e45365a5914e00bc0be (diff) | |
download | linux-8176117b82e49e043d045f214ba7a892fba6b827.tar.gz linux-8176117b82e49e043d045f214ba7a892fba6b827.tar.bz2 linux-8176117b82e49e043d045f214ba7a892fba6b827.zip |
lightnvm: manage lun partitions internally in mm
LUNs are exclusively owned by targets implementing a block device FTL.
Doing this reservation requires at the moment a 2-way callback gennvm
<-> target. The reason behind this is that LUNs were not assumed to
always be exclusively owned by targets. However, this design decision
goes against I/O determinism QoS (two targets would mix I/O on the same
parallel unit in the device).
This patch makes LUN reservation as part of the target creation on the
media manager. This makes that LUNs are always exclusively owned by the
target instantiated on top of them. LUN stripping and/or sharing should
be implemented on the target itself or the layers on top.
Signed-off-by: Javier González <javier@cnexlabs.com>
Signed-off-by: Matias Bjørling <m@bjorling.me>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'drivers/nvme')
0 files changed, 0 insertions, 0 deletions