diff options
| author | John Baldwin <jhb@FreeBSD.org> | 2024-05-02 23:29:37 +0000 |
|---|---|---|
| committer | John Baldwin <jhb@FreeBSD.org> | 2024-05-02 23:29:37 +0000 |
| commit | a1eda74167b5edb99fd31d507d8a3f7d7e14ae2b (patch) | |
| tree | f33f86bb8a589ab652035119ecc57e6916a6e13e /sys/dev/nvmf/controller | |
| parent | 07c6a62bab69296f2514dc99046ac701c4392f78 (diff) | |
nvmf: The in-kernel NVMe over Fabrics host
This is the client (initiator in SCSI terms) for NVMe over Fabrics.
Userland is responsible for creating a set of queue pairs and then
handing them off via an ioctl to this driver, e.g. via the 'connect'
command from nvmecontrol(8). An nvmeX new-bus device is created
at the top-level to represent the remote controller similar to PCI
nvmeX devices for PCI-express controllers.
As with nvme(4), namespace devices named /dev/nvmeXnsY are created and
pass through commands can be submitted to either the namespace devices
or the controller device. For example, 'nvmecontrol identify nvmeX'
works for a remote Fabrics controller the same as for a PCI-express
controller.
nvmf exports remote namespaces via nda(4) devices using the new NVMF
CAM transport. nvmf does not support nvd(4), only nda(4).
Sponsored by: Chelsio Communications
Differential Revision: https://reviews.freebsd.org/D44714
Diffstat (limited to 'sys/dev/nvmf/controller')
0 files changed, 0 insertions, 0 deletions