diff options
author | Igor Konopko <igor.j.konopko@intel.com> | 2019-05-04 20:37:55 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2019-05-06 10:19:17 -0600 |
commit | a14669ebc0e294f19b2290c294958b7741559d9d (patch) | |
tree | 833538849f051b5ebe5ba8509a64453ef7653e6d /drivers/lightnvm/pblk-init.c | |
parent | d38954ed1b76a2814057cd4af92c6966bceb3d3c (diff) | |
download | linux-stable-a14669ebc0e294f19b2290c294958b7741559d9d.tar.gz linux-stable-a14669ebc0e294f19b2290c294958b7741559d9d.tar.bz2 linux-stable-a14669ebc0e294f19b2290c294958b7741559d9d.zip |
lightnvm: Inherit mdts from the parent nvme device
Current lightnvm and pblk implementation does not care about NVMe max
data transfer size, which can be smaller than 64*K=256K. There are
existing NVMe controllers which NVMe max data transfer size is lower
that 256K (for example 128K, which happens for existing NVMe
controllers which are NVMe spec compliant). Such a controllers are not
able to handle command which contains 64 PPAs, since the the size of
DMAed buffer will be above the capabilities of such a controller.
Signed-off-by: Igor Konopko <igor.j.konopko@intel.com>
Reviewed-by: Hans Holmberg <hans.holmberg@cnexlabs.com>
Reviewed-by: Javier González <javier@javigon.com>
Signed-off-by: Matias Bjørling <mb@lightnvm.io>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/lightnvm/pblk-init.c')
0 files changed, 0 insertions, 0 deletions