en Copyright 2015 Java http://kernelsources.org:8080/source/history/freebsd/lib/libnvmf/Makefile#1a80bcc5fafaa822e281bf963e7c58a8747a610c Remove redundant PACKAGE for INTERNALLIB librariesThese libraries don't install anything, so they shouldn't have aPACKAGE setting. This avoids surprising behaviour in future ife.g. manpages are added to an internal library.Reported by: desDifferential Revision: https://reviews.freebsd.org/D51901 List of files: /freebsd/lib/libnvmf/Makefile Sat, 23 Aug 2025 01:51:13 +0200 Lexi Winter <ivy@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/lib/libnvmf/Makefile#365b89e8ea4af34a05f68aa28e77573e89fa00b2 nvmf: Switch several ioctls to using nvlistsFor requests that handoff queues from userspace to the kernel as wellas the request to fetch reconnect parameters from the kernel, switchfrom using flat structures to nvlists. In particular, this willpermit adding support for additional transports in the future withoutbreaking the ABI of the structures.Note that this is an ABI break for the ioctls used by nvmf(4) andnvmft(4). Since this is only present in main I did not botherimplementing compatability shims.Inspired by: imp (suggestion on a different review)Reviewed by: impSponsored by: Chelsio CommunicationsDifferential Revision: https://reviews.freebsd.org/D48230 List of files: /freebsd/lib/libnvmf/Makefile Mon, 30 Dec 2024 19:52:21 +0100 John Baldwin <jhb@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/lib/libnvmf/Makefile#2da066ef6d85d3f7cd8aaec14369d66254836536 libnvmf: Add internal library to support NVMe over Fabricslibnvmf provides APIs for transmitting and receiving Command andResponse capsules along with data associated with NVMe commands.Capsules are represented by 'struct nvmf_capsule' objects.Capsules are transmitted and received on queue pairs represented by'struct nvmf_qpair' objects.Queue pairs belong to an association represented by a 'structnvmf_association' object.libnvmf provides additional helper APIs to assist with constructingcommand capsules for a host, response capsules for a controller,connecting queue pairs to a remote controller and optionallyoffloading connected queues to an in-kernel host, accepting queue pairconnections from remote hosts and optionally offloading connectedqueues to an in-kernel controller, constructing controller datastructures for local controllers, etc.libnvmf also includes an internal transport abstraction as well as animplementation of a userspace TCP transport.libnvmf is primarily intended for ease of use and low-traffic use casessuch as establishing connections that are handed off to the kernel.As such, it uses a simple API built on blocking I/O.For a host, a consumer first populates an 'structnvmf_association_params' with a set of parameters shared by all queuepairs for a single association such as whether or not to use SQ flowcontrol and header and data digests and creates a 'structnvmf_association' object. The consumer is responsible forestablishing a TCP socket for each queue pair. This socket isincluded in the 'struct nvmf_qpair_params' passed to 'nvmf_connect' tocomplete transport-specific negotiation, send a Fabrics Connectcommand, and wait for the Connect reply. Upon success, a new 'structnvmf_qpair' object is returned. This queue pair can then be used tosend and receive capsules. A command capsule is allocated, populatedwith an SQE and optional data buffer, and transmitted vianvmf_host_transmit_command. The consumer can then wait for a replyvia nvmf_host_wait_for_response. The library also provides somewrapper functions such as nvmf_read_property and nvmf_write_propertywhich send a command and wait for a response synchronously.For a controller, a consumer uses a single association for a set ofincoming connections. A consumer can choose to use multipleassociations (e.g. a separate association for connections to adiscovery controller listening on a different port than I/Ocontrollers). The consumer is responsible for accepting TCP socketsdirectly, but once a socket has been accepted it is passed tonvmf_accept to perform transport-specific negotiation and wait for theConnect command. Similar to nvmf_connect, nvmf_accept returns a newlyconstruct nvmf_qpair. However, in contrast to nvmf_connect,nvmf_accept does not complete the Fabrics negotiation. The consumermust explicitly send a response capsule before waiting for additionalcommand capsules to arrive. In particular, in the kernel offloadcase, the Connect command and data are provided to the kernelcontroller and the Connect response capsule is sent by the kernel onceit is ready to handle the new queue pair.For userspace controller command handling, the consumer usesnvmf_controller_receive_capsule to wait for a command capsule.nvmf_receive_controller_data is used to retrieve any data from acommand (e.g. the data for a WRITE command). It can be calledmultiple times to split the data transfer into smaller sizes.nvmf_send_controller_data is used to send data to a remote host inresponse to a command. It also sends a response capsule indicatingsuccess, or an error if an internal error occurs. nvmf_send_responseis used to send a response without associated data. There are alsoseveral convenience wrappers such as nvmf_send_success andnvmf_send_generic_error.Reviewed by: impSponsored by: Chelsio CommunicationsDifferential Revision: https://reviews.freebsd.org/D44710 List of files: /freebsd/lib/libnvmf/Makefile Fri, 03 May 2024 01:28:16 +0200 John Baldwin <jhb@FreeBSD.org>