Jim Harris 8d09e3c400 Use MAXPHYS to specify the maximum I/O size for nvme(4). ...

Also allow admin commands to transfer up to this maximum I/O size, rather
than the artificial limit previously imposed.  The larger I/O size is very
beneficial for upcoming firmware download support.  This has the added
benefit of simplifying the code since both admin and I/O commands now use
the same maximum I/O size.

Sponsored by:	Intel
MFC after:	3 days

2013-06-26 23:27:17 +00:00

..

nvme_ctrlr_cmd.c

Add "type" to nvme_request, signifying if its payload is a VADDR, UIO, or

2013-03-29 20:34:28 +00:00

nvme_ctrlr.c

Use MAXPHYS to specify the maximum I/O size for nvme(4).

2013-06-26 23:27:17 +00:00

nvme_ns_cmd.c

Add unmapped bio support to nvme(4) and nvd(4).

2013-04-01 16:23:34 +00:00

nvme_ns.c

Remove the NVME_IDENTIFY_CONTROLLER and NVME_IDENTIFY_NAMESPACE IOCTLs and replace

2013-04-12 17:56:47 +00:00

nvme_private.h

Use MAXPHYS to specify the maximum I/O size for nvme(4).

2013-06-26 23:27:17 +00:00

nvme_qpair.c

Use MAXPHYS to specify the maximum I/O size for nvme(4).

2013-06-26 23:27:17 +00:00

nvme_sysctl.c

Remove the is_started flag from struct nvme_controller.

2013-03-26 21:19:26 +00:00

nvme_test.c

Change a number of malloc(9) calls to use M_WAITOK instead of

2013-03-26 22:11:34 +00:00

nvme.c

Move the busdma mapping functions to nvme_qpair.c.

2013-04-12 17:48:45 +00:00

nvme.h

Use MAXPHYS to specify the maximum I/O size for nvme(4).

2013-06-26 23:27:17 +00:00