summaryrefslogtreecommitdiffstats
path: root/share/man/man4/nvme.4
Commit message (Collapse)AuthorAgeFilesLines
* MFC r293352:jimharris2016-01-111-3/+15
| | | | | | | | | | | | | | | | | | | | | | nvme: add hw.nvme.min_cpus_per_ioq tunable Due to FreeBSD system-wide limits on number of MSI-X vectors (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199321), it may be desirable to allocate fewer than the maximum number of vectors for an NVMe device, in order to save vectors for other devices (usually Ethernet) that can take better advantage of them and may be probed after NVMe. This tunable is expressed in terms of minimum number of CPUs per I/O queue instead of max number of queues per controller, to allow for a more even distribution of CPUs per queue. This avoids cases where some number of CPUs have a dedicated queue, but other CPUs need to share queues. Ideally the PR referenced above will eventually be fixed and the mechanism implemented here becomes obsolete anyways. While here, fix a bug in the CPUs per I/O queue calculation to properly account for the admin queue's MSI-X vector.
* MFC r263303:jimharris2014-05-071-5/+8
| | | | | Update nvme(4) and nvd(4) man pages to clarify the differences between their respective device nodes.
* MFC: r262603brueffer2014-03-071-4/+9
| | | | mdoc cleanup.
* Bump date for nvme(4) and nvd(4).jimharris2013-07-111-1/+1
| | | | MFC after: 3 days
* Update nvme(4) and nvd(4) to reflect recent work and upcoming inclusionjimharris2013-07-091-17/+6
| | | | | | | in 9.2 release. Sponsored by: Intel MFC after: 3 days
* Remove whitespace.joel2012-10-121-1/+1
|
* Add man pages for nvme(4) and nvd(4).jimharris2012-10-101-0/+175
Sponsored by: Intel Reviewed by: joel
OpenPOWER on IntegriCloud