src-test2/sys/dev/nvd, branch release/10.0.0 FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F10.0.0 2013-10-08T15:44:04Z Add driver-assisted striping for upcoming Intel NVMe controllers that can 2013-10-08T15:44:04Z Jim Harris jimharris@FreeBSD.org 2013-10-08T15:44:04Z urn:sha1:a40e72a695a5db6cf9c6da148e8e8c26158e29b3 benefit from it. Sponsored by: Intel Reviewed by: kib (earlier version), carl Approved by: re (hrs) MFC after: 1 week Add message when nvd disks are attached and detached. 2013-07-19T21:40:57Z Jim Harris jimharris@FreeBSD.org 2013-07-19T21:40:57Z urn:sha1:38441bd9a978287f0f37911afc046add95cc187c As part of this commit, add an nvme_strvis() function which borrows heavily from cam_strvis(). This will allow stripping of leading/trailing whitespace and also handle unprintable characters in model/serial numbers. This function goes into a new nvme_util.c file which is used by both the driver and nvmecontrol. Sponsored by: Intel Reviewed by: carl MFC after: 3 days Do not call disk_create() until we have completed all initialization of our 2013-07-19T21:30:53Z Jim Harris jimharris@FreeBSD.org 2013-07-19T21:30:53Z urn:sha1:c3e9dd893b9a79c6949803a45ac36910313499dd internal disk structure. Sponsored by: Intel Reviewed by: carl MFC after: 3 days Define constants for the lengths of the serial number, model number 2013-07-17T23:23:38Z Jim Harris jimharris@FreeBSD.org 2013-07-17T23:23:38Z urn:sha1:e8f25c62665641079669d81859959684cba932a6 and firmware revision in the controller's identify structure. Also modify consumers of these fields to ensure they only use the specified number of bytes for their respective fields. Sponsored by: Intel Reviewed by: carl MFC after: 3 days Update copyright dates. 2013-07-09T21:22:17Z Jim Harris jimharris@FreeBSD.org 2013-07-09T21:22:17Z urn:sha1:e9efbc134ff240560d3a23c68b97129a5923eda1 MFC after: 3 days Add unmapped bio support to nvme(4) and nvd(4). 2013-04-01T16:23:34Z Jim Harris jimharris@FreeBSD.org 2013-04-01T16:23:34Z urn:sha1:5fdf9c3c8e3d386b57f96f71566ea53730015219 Sponsored by: Intel Change a number of malloc(9) calls to use M_WAITOK instead of 2013-03-26T22:11:34Z Jim Harris jimharris@FreeBSD.org 2013-03-26T22:11:34Z urn:sha1:237d2019e5b3b1e6221f1f891f71c2d9ccf33a9a M_NOWAIT. Sponsored by: Intel Suggested by: carl Reviewed by: carl Add the ability to internally mark a controller as failed, if it is unable to 2013-03-26T21:58:38Z Jim Harris jimharris@FreeBSD.org 2013-03-26T21:58:38Z urn:sha1:232e2edb6cd50465bd62b9f7cbc9fd83531c02ca start or reset. Also add a notifier for NVMe consumers for controller fail conditions and plumb this notifier for nvd(4) to destroy the associated GEOM disks when a failure occurs. This requires a bit of work to cover the races when a consumer is sending I/O requests to a controller that is transitioning to the failed state. To help cover this condition, add a task to defer completion of I/Os submitted to a failed controller, so that the consumer will still always receive its completions in a different context than the submission. Sponsored by: Intel Reviewed by: carl Have nvd(4) register for controller notifications. 2013-03-26T21:45:37Z Jim Harris jimharris@FreeBSD.org 2013-03-26T21:45:37Z urn:sha1:ec84ecbba0ef8e3314ea5ec51ff8dcd6c0761bd9 Also have nvd maintain controller/namespace relationships internally. Sponsored by: Intel Reviewed by: carl Create struct nvme_status. 2013-03-26T21:00:18Z Jim Harris jimharris@FreeBSD.org 2013-03-26T21:00:18Z urn:sha1:cf81529ce39c2f772229cd228cbace17c6669fb3 NVMe error log entries include status, so breaking this out into its own data structure allows it to be included in both the nvme_completion data structure as well as error log entry data structures. While here, expose nvme_completion_is_error(), and change all of the places that were explicitly looking at sc/sct bits to use this macro instead. Sponsored by: Intel Reviewed by: carl