#
399362ba |
| 25-Jul-2024 |
John Baldwin <jhb@FreeBSD.org> |
nvmfd: Permit setting the MAXH2CDATA value via -H
This value is advertised to the remote host for TCP associations and determines the maximum data payload size the remote host is permitted to transm
nvmfd: Permit setting the MAXH2CDATA value via -H
This value is advertised to the remote host for TCP associations and determines the maximum data payload size the remote host is permitted to transmit in a single PDU.
Sponsored by: Chelsio Communications
show more ...
|
#
6549718b |
| 25-Jul-2024 |
John Baldwin <jhb@FreeBSD.org> |
nvmfd: Stop setting MAXR2T in association parameters
This is only used for the host side of an association. The controller obtains this value from the host during connection negotiation.
Sponsored
nvmfd: Stop setting MAXR2T in association parameters
This is only used for the host side of an association. The controller obtains this value from the host during connection negotiation.
Sponsored by: Chelsio Communications
show more ...
|
#
a8089ea5 |
| 03-May-2024 |
John Baldwin <jhb@FreeBSD.org> |
nvmfd: A simple userspace daemon for the NVMe over Fabrics controller
This daemon can operate as a purely userspace controller exporting one or more simulated RAM disks or local block devices as NVM
nvmfd: A simple userspace daemon for the NVMe over Fabrics controller
This daemon can operate as a purely userspace controller exporting one or more simulated RAM disks or local block devices as NVMe namespaces to a remote host. In this case the daemon provides a discovery controller with a single entry for an I/O controller.
nvmfd can also offload I/O controller queue pairs to the nvmft.ko in-kernel Fabrics controller when -K is passed. In this mode, nvmfd still accepts connections and performs initial transport-specific negotitation in userland. The daemon still provides a userspace-only discovery controller with a single entry for an I/O controller. However, queue pairs for the I/O controller are handed off to the CTL NVMF frontend.
Eventually ctld(8) should be refactored to to provide an abstraction for the frontend protocol and the discovery and the kernel mode of this daemon should be merged into ctld(8). At that point this daemon can be moved to tools/tools/nvmf as a debugging tool (mostly as sample code for a userspace controller using libnvmf).
Reviewed by: imp Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D44731
show more ...
|