jimharris 63beb43e5f Remove the is_started flag from struct nvme_controller. ...

This flag was originally added to communicate to the sysctl code
which oids should be built, but there are easier ways to do this.  This
needs to be cleaned up prior to adding new controller states - for example,
controller failure.

Sponsored by:	Intel
Reviewed by:	carl

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

..

nvme_ctrlr_cmd.c

Add structure definitions and controller command function for firmware

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

nvme_ctrlr.c

Remove the is_started flag from struct nvme_controller.

2013-03-26 21:19:26 +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_ns.c

Create struct nvme_status.

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

nvme_private.h

Remove the is_started flag from struct nvme_controller.

2013-03-26 21:19:26 +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

Remove the is_started flag from struct nvme_controller.

2013-03-26 21:19:26 +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

nvme.c

Remove the is_started flag from struct nvme_controller.

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

nvme.h

Pass associated log page data to async event consumers, if requested.

2013-03-26 21:08:32 +00:00