Alexander Motin ee7f4d8187 Revert r292074 (by smh): Limit stripesize reported from nvd(4) to 4K ... I believe that this patch handled the problem from the wrong side. Instead of making ZFS properly handle large stripe sizes, it made unrelated driver to lie in reported parameters to workaround that. Alternative solution for this problem from ZFS side was committed at r296615. Discussed with: smh		2016-03-10 17:13:10 +00:00
..
nvme_ctrlr_cmd.c	Use bitwise OR instead of logical OR when constructing value for	2014-06-10 21:40:43 +00:00
nvme_ctrlr.c	nvme: fix intx handler to not dereference ioq during initialization	2016-02-24 00:01:10 +00:00
nvme_ns_cmd.c
nvme_ns.c	Revert r292074 (by smh): Limit stripesize reported from nvd(4) to 4K	2016-03-10 17:13:10 +00:00
nvme_private.h	nvme: do not revert o single I/O queue when per-CPU queues not possible	2016-01-07 16:18:32 +00:00
nvme_qpair.c	nvme: do not pre-allocate MSI-X IRQ resources	2016-01-07 16:11:31 +00:00
nvme_sysctl.c	Revert r292074 (by smh): Limit stripesize reported from nvd(4) to 4K	2016-03-10 17:13:10 +00:00
nvme_test.c	Extend some 32-bit fields and variables to 64-bit to prevent overflow	2013-10-08 15:47:22 +00:00
nvme_util.c
nvme.c	nvme: do not revert o single I/O queue when per-CPU queues not possible	2016-01-07 16:18:32 +00:00
nvme.h	Revert r292074 (by smh): Limit stripesize reported from nvd(4) to 4K	2016-03-10 17:13:10 +00:00