#
285830 |
|
23-Jul-2015 |
gjb |
- Copy stable/10@285827 to releng/10.2 in preparation for 10.2-RC1 builds. - Update newvers.sh to reflect RC1. - Update __FreeBSD_version to reflect 10.2. - Update default pkg(8) configuration to use the quarterly branch.[1]
Discussed with: re, portmgr [1] Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
282926 |
|
14-May-2015 |
jimharris |
MFC r281283:
nvme: remove CHATHAM related code
Chatham was an internal NVMe prototype board used for early driver development.
Sponsored by: Intel
|
#
282925 |
|
14-May-2015 |
jimharris |
MFC r281282:
nvme: add device strings for Intel DC series NVMe SSDs
Sponsored by: Intel
|
#
265576 |
|
07-May-2014 |
jimharris |
MFC r263310:
nvme: Close hole where nvd(4) would not be notified of all nvme(4) instances if modules loaded during boot.
|
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
256155 |
|
08-Oct-2013 |
jimharris |
Do not leak resources during attach if nvme_ctrlr_construct() or the initial controller resets fail.
Sponsored by: Intel Reviewed by: carl Approved by: re (hrs) MFC after: 1 week
|
#
254303 |
|
13-Aug-2013 |
jimharris |
If a controller fails to initialize, do not notify consumers (nvd) of its namespaces.
Sponsoredy by: Intel Reviewed by: carl MFC after: 3 days
|
#
254302 |
|
13-Aug-2013 |
jimharris |
Send a shutdown notification in the driver unload path, to ensure notification gets sent in cases where system shuts down with driver unloaded.
Sponsored by: Intel Reviewed by: carl MFC after: 3 days
|
#
253476 |
|
19-Jul-2013 |
jimharris |
Add message when nvd disks are attached and detached.
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
|
#
253112 |
|
09-Jul-2013 |
jimharris |
Update copyright dates.
MFC after: 3 days
|
#
253107 |
|
09-Jul-2013 |
jimharris |
Add pci_enable_busmaster() and pci_disable_busmaster() calls in nvme_attach() and nvme_detach() respectively.
Sponsored by: Intel MFC after: 3 days
|
#
249420 |
|
12-Apr-2013 |
jimharris |
Move the busdma mapping functions to nvme_qpair.c.
This removes nvme_uio.c completely.
Sponsored by: Intel
|
#
249416 |
|
12-Apr-2013 |
jimharris |
Do not panic when a busdma mapping operation fails.
Instead, print an error message and fail the associated command with DATA_TRANSFER_ERROR NVMe completion status.
Sponsored by: Intel
|
#
248769 |
|
26-Mar-2013 |
jimharris |
Replace usages of mtx_pool_find used for admin commands with a polling mechanism.
Now that all requests are timed, we are guaranteed to get a completion notification, even if it is an abort status due to a timed out admin command.
This has the effect of simplifying the controller and namespace setup code, so that it reads straight through rather than broken up into a bunch of different callback functions.
Sponsored by: Intel Reviewed by: carl
|
#
248767 |
|
26-Mar-2013 |
jimharris |
Add the ability to internally mark a controller as failed, if it is unable to 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
|
#
248763 |
|
26-Mar-2013 |
jimharris |
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
|
#
248761 |
|
26-Mar-2013 |
jimharris |
Cap the number of retry attempts to a configurable number. This ensures that if a specific I/O repeatedly times out, we don't retry it indefinitely.
The default number of retries will be 4, but is adjusted using hw.nvme.retry_count.
Sponsored by: Intel Reviewed by: carl
|
#
248760 |
|
26-Mar-2013 |
jimharris |
Pass associated log page data to async event consumers, if requested.
Sponsored by: Intel Reviewed by: carl
|
#
248756 |
|
26-Mar-2013 |
jimharris |
Create struct nvme_status.
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
|
#
248746 |
|
26-Mar-2013 |
jimharris |
Add controller reset capability to nvme(4) and ability to explicitly invoke it from nvmecontrol(8).
Controller reset will be performed in cases where I/O are repeatedly timing out, the controller reports an unrecoverable condition, or when explicitly requested via IOCTL or an nvme consumer. Since the controller may be in such a state where it cannot even process queue deletion requests, we will perform a controller reset without trying to clean up anything on the controller first.
Sponsored by: Intel Reviewed by: carl
|
#
248738 |
|
26-Mar-2013 |
jimharris |
Add an interface for nvme shim drivers (i.e. nvd) to register for notifications when new nvme controllers are added to the system.
Sponsored by: Intel
|
#
248736 |
|
26-Mar-2013 |
jimharris |
Move controller destruction code from nvme_detach() to new nvme_ctrlr_destruct() function.
Sponsored by: Intel
|
#
247963 |
|
07-Mar-2013 |
obrien |
Fix GCC build: /usr/src/sys/modules/nvme/../../dev/nvme/nvme.c:211: warning: format '%qx' expects type 'long unsigned int', but argument 9 has type 'long long unsigned int' [-Wformat]
|
#
244413 |
|
18-Dec-2012 |
jimharris |
Map BAR 4/5, because NVMe spec says devices may place the MSI-X table behind BAR 4/5, rather than in BAR 0/1 with the control/doorbell registers.
Sponsored by: Intel
|
#
244411 |
|
18-Dec-2012 |
jimharris |
Simplify module definition by adding nvme_modevent to DRIVER_MODULE() definition.
Submitted by: Carl Delsey <carl.r.delsey@intel.com>
|
#
244410 |
|
18-Dec-2012 |
jimharris |
Do not use taskqueue to defer completion work when using INTx. INTx now matches MSI-X behavior.
Sponsored by: Intel
|
#
243951 |
|
06-Dec-2012 |
jimharris |
Add PCI device ID for 8-channel IDT NVMe controller, and clarify that the previously defined IDT PCI device ID was for a 32-channel controller.
Submitted by: Joe Golio <joseph.golio@isilon.com>
|
#
241661 |
|
18-Oct-2012 |
jimharris |
Cleanup uio-related code to use struct nvme_request and nvme_ctrlr_submit_io_request().
While here, also fix case where a uio may have more than 1 iovec. NVMe's definition of SGEs (called PRPs) only allows for the first SGE to start on a non-page boundary. The simplest way to handle this is to construct a temporary uio for each iovec, and submit an NVMe request for each.
Sponsored by: Intel
|
#
241660 |
|
18-Oct-2012 |
jimharris |
Add nvme_ctrlr_submit_[admin|io]_request functions which consolidates code for allocating nvme_tracker objects and making calls into bus_dmamap_load for commands which have payloads.
Sponsored by: Intel
|
#
241659 |
|
18-Oct-2012 |
jimharris |
Add struct nvme_request object which contains all of the parameters passed from an NVMe consumer.
This allows us to mostly build NVMe command buffers without holding the qpair lock, and also allows for future queueing of nvme_request objects in cases where the submission queue is full and no nvme_tracker objects are available.
Sponsored by: Intel
|
#
241658 |
|
18-Oct-2012 |
jimharris |
Merge struct nvme_prp_list into struct nvme_tracker.
This simplifies the driver significantly where it is constructing commands to be submitted to hardware. By reducing the number of PRPs (NVMe parlance for SGE) from 128 to 32, it ensures we do not allocate too much memory for more common smaller I/O sizes, while still supporting up to 128KB I/O sizes.
This also paves the way for pre-allocation of nvme_tracker objects for each queue which will simplify the I/O path even further.
Sponsored by: Intel
|
#
241657 |
|
18-Oct-2012 |
jimharris |
Add return codes to all functions used for submitting commands to I/O queues.
Sponsored by: Intel
|
#
241394 |
|
10-Oct-2012 |
kevlo |
Revert previous commit...
Pointyhat to: kevlo (myself)
|
#
241370 |
|
09-Oct-2012 |
kevlo |
Prefer NULL over 0 for pointers
|
#
240700 |
|
19-Sep-2012 |
jimharris |
In nvme(4), set device description for BUS_PROBE_GENERIC case.
Reported by: jhb
|
#
240697 |
|
19-Sep-2012 |
jimharris |
Report nvme(4) as a generic driver for NVMe devices if PCI class, subclass and programming interface codes match.
Sponsored by: Intel
|
#
240616 |
|
17-Sep-2012 |
jimharris |
This is the first of several commits which will add NVM Express (NVMe) support to FreeBSD. A full description of the overall functionality being added is below. nvmexpress.org defines NVM Express as "an optimized register interface, command set and feature set fo PCI Express (PCIe)-based Solid-State Drives (SSDs)."
This commit adds nvme(4) and nvd(4) driver source code and Makefiles to the tree.
Full NVMe functionality description: Add nvme(4) and nvd(4) drivers and nvmecontrol(8) for NVM Express (NVMe) device support.
There will continue to be ongoing work on NVM Express support, but there is more than enough to allow for evaluation of pre-production NVM Express devices as well as soliciting feedback. Questions and feedback are welcome.
nvme(4) implements NVMe hardware abstraction and is a provider of NVMe namespaces. The closest equivalent of an NVMe namespace is a SCSI LUN. nvd(4) is an NVMe consumer, surfacing NVMe namespaces as GEOM disks. nvmecontrol(8) is used for NVMe configuration and management.
The following are currently supported: nvme(4) - full mandatory NVM command set support - per-CPU IO queues (enabled by default but configurable) - per-queue sysctls for statistics and full command/completion queue dumps for debugging - registration API for NVMe namespace consumers - I/O error handling (except for timeoutsee below) - compilation switches for support back to stable-7
nvd(4) - BIO_DELETE and BIO_FLUSH (if supported by controller) - proper BIO_ORDERED handling
nvmecontrol(8) - devlist: list NVMe controllers and their namespaces - identify: display controller or namespace identify data in human-readable or hex format - perftest: quick and dirty performance test to measure raw performance of NVMe device without userspace/physio/GEOM overhead
The following are still work in progress and will be completed over the next 3-6 months in rough priority order: - complete man pages - firmware download and activation - asynchronous error requests - command timeout error handling - controller resets - nvmecontrol(8) log page retrieval
This has been primarily tested on amd64, with light testing on i386. I would be happy to provide assistance to anyone interested in porting this to other architectures, but am not currently planning to do this work myself. Big-endian and dmamap sync for command/completion queues are the main areas that would need to be addressed.
The nvme(4) driver currently has references to Chatham, which is an Intel-developed prototype board which is not fully spec compliant. These references will all be removed over time.
Sponsored by: Intel Contributions from: Joe Golio/EMC <joseph dot golio at emc dot com>
|