---
name: "nvmft"
section: "4"
platform: "freebsd"
package: "base"
version: "16.0-CURRENT-20261027-61c70dc16a79"
release: "FreeBSD 16.0-CURRENT (2026-10-27)"
platforms: ["freebsd"]
url: "https://new.carta.tech/nvmft"
---

# nvmft(4)

NVM Express over Fabrics CAM Target Layer frontend

## NAME

**nvmft** – NVM Express over Fabrics CAM Target Layer frontend

## SYNOPSIS

To compile the subsystem into the kernel, place the following lines in the kernel configuration file:

**device nvmft** **device ctl**

Alternatively, to load the subsystem as a module at boot time, place the following line in [loader.conf(5)](/loader.conf/5.md):

```
nvmft_load="YES"
```

## DESCRIPTION

The **nvmft** driver provides the kernel component of an NVM Express over Fabrics controller. The NVMeoF controller is the server exporting namespaces backed by local files and volumes to remote hosts. **nvmft** follows the dynamic controller model and creates a new dynamic controller for each association.

**nvmft** is implemented as a [ctl(4)](/ctl/4.md) frontend and exports CAM Target Layer LUNs as namespaces to remote hosts. LUNs can be configured via [ctladm(8)](/ctladm/8.md).

Associations between the local controller and remote hosts are managed using both the nvmfd(8) daemon and the [ctladm(8)](/ctladm/8.md) utility. The nvmfd(8) daemon listens for new associations and handles transport-specific negotiation before handing off connected queue pairs to **nvmft** which associates queue pairs with a suitable controller instance. The **nvlist** [ctladm(8)](/ctladm/8.md) command lists active controllers. The **nvterminate** command terminates one or more associations between a local controller and a remote host.

Associations require a supported transport such as [nvmf\_tcp(4)](/nvmf_tcp/4.md) for associations using TCP/IP.

## SEE ALSO

[ctl(4)](/ctl/4.md), [nvmf(4)](/nvmf/4.md), [nvmf\_tcp(4)](/nvmf_tcp/4.md), [ctladm(8)](/ctladm/8.md), nvmfd(8)

## HISTORY

The **nvmft** module first appeared in FreeBSD 15.0.

## AUTHORS

The **nvmft** subsystem was developed by John Baldwin ⟨*jhb@FreeBSD.org*⟩ under sponsorship from Chelsio Communications, Inc.