Jim Harris 02e3348484 Ensure the controller's MDTS is accounted for in max_xfer_size. ... The controller's IDENTIFY data contains MDTS (Max Data Transfer Size) to allow the controller to specify the maximum I/O data transfer size. nvme(4) already provides a default maximum, but make sure it does not exceed what MDTS reports. Sponsored by: Intel Reviewed by: carl		2013-03-26 21:16:53 +00:00
..
nvme.c	Cap the number of retry attempts to a configurable number. This ensures	2013-03-26 21:14:51 +00:00
nvme.h	Pass associated log page data to async event consumers, if requested.	2013-03-26 21:08:32 +00:00
nvme_ctrlr.c	Ensure the controller's MDTS is accounted for in max_xfer_size.	2013-03-26 21:16:53 +00:00
nvme_ctrlr_cmd.c	Add structure definitions and controller command function for firmware	2013-03-26 21:03:03 +00:00
nvme_ns.c	Create struct nvme_status.	2013-03-26 21:00:18 +00:00
nvme_ns_cmd.c	Make the DSM range count 0-based. Previously we were deallocating one more	2013-03-26 18:16:30 +00:00
nvme_private.h	Ensure the controller's MDTS is accounted for in max_xfer_size.	2013-03-26 21:16:53 +00:00
nvme_qpair.c	Cap the number of retry attempts to a configurable number. This ensures	2013-03-26 21:14:51 +00:00
nvme_sysctl.c	Add a tunable for the I/O timeout interval. Default is still 30 seconds,	2013-03-26 20:02:35 +00:00
nvme_test.c	Create struct nvme_status.	2013-03-26 21:00:18 +00:00
nvme_uio.c	Create struct nvme_status.	2013-03-26 21:00:18 +00:00