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/nvme | |
| parent | lightnvm: pblk: set proper read status in bio (diff) | |
| download | linux-dev-a14669ebc0e294f19b2290c294958b7741559d9d.tar.xz linux-dev-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/nvme')
| -rw-r--r-- | drivers/nvme/host/lightnvm.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/nvme/host/lightnvm.c b/drivers/nvme/host/lightnvm.c index 949e29e1d782..4f20a10b39d3 100644 --- a/drivers/nvme/host/lightnvm.c +++ b/drivers/nvme/host/lightnvm.c @@ -977,6 +977,7 @@ int nvme_nvm_register(struct nvme_ns *ns, char *disk_name, int node) geo->csecs = 1 << ns->lba_shift; geo->sos = ns->ms; geo->ext = ns->ext; + geo->mdts = ns->ctrl->max_hw_sectors; dev->q = q; memcpy(dev->name, disk_name, DISK_NAME_LEN); |