Changes in Makefile

0faa0fe6 - nvmet: New NVMe PCI endpoint function target driver

Sat, 04 Jan 2025 04:59:50 +0000

nvmet: New NVMe PCI endpoint function target driverImplement a PCI target driver using the PCI endpoint framework. Thisrequires hardware with a PCI controller capable of executing in endpointmode.The PCI endpoint framework is used to set up a PCI endpoint functionand its BAR compatible with a NVMe PCI controller. The framework is alsoused to map local memory to the PCI address space to execute MMIOaccesses for retrieving NVMe commands from submission queues and postingcompletion entries to completion queues. If supported, DMA is used forcommand retreival and command data transfers, based on the PCI addresssegments indicated by the command using either PRPs or SGLs.The NVMe target driver relies on the NVMe target core code to executeall commands isssued by the host. The PCI target driver is mainlyresponsible for the following: - Initialization and teardown of the endpoint device and its backend PCI target controller. The PCI target controller is created using a subsystem and a port defined through configfs. The port used must be initialized with the "pci" transport type. The target controller is allocated and initialized when the PCI endpoint is started by binding it to the endpoint PCI device (nvmet_pci_epf_epc_init() function). - Manage the endpoint controller state according to the PCI link state and the actions of the host (e.g. checking the CC.EN register) and propagate these actions to the PCI target controller. Polling of the controller enable/disable is done using a delayed work scheduled every 5ms (nvmet_pci_epf_poll_cc() function). This work is started whenever the PCI link comes up (nvmet_pci_epf_link_up() notifier function) and stopped when the PCI link comes down (nvmet_pci_epf_link_down() notifier function). nvmet_pci_epf_poll_cc() enables and disables the PCI controller using the functions nvmet_pci_epf_enable_ctrl() and nvmet_pci_epf_disable_ctrl(). The controller admin queue is created using nvmet_pci_epf_create_cq(), which calls nvmet_cq_create(), and nvmet_pci_epf_create_sq() which uses nvmet_sq_create(). nvmet_pci_epf_disable_ctrl() always resets the PCI controller to its initial state so that nvmet_pci_epf_enable_ctrl() can be called again. This ensures correct operation if, for instance, the host reboots causing the PCI link to be temporarily down. - Manage the controller admin and I/O submission queues using local memory. Commands are obtained from submission queues using a work item that constantly polls the doorbells of all submissions queues (nvmet_pci_epf_poll_sqs() function). This work is started whenever the controller is enabled (nvmet_pci_epf_enable_ctrl() function) and stopped when the controller is disabled (nvmet_pci_epf_disable_ctrl() function). When new commands are submitted by the host, DMA transfers are used to retrieve the commands. - Initiate the execution of all admin and I/O commands using the target core code, by calling a requests execute() function. All commands are individually handled using a per-command work item (nvmet_pci_epf_iod_work() function). A command overall execution includes: initializing a struct nvmet_req request for the command, using nvmet_req_transfer_len() to get a command data transfer length, parse the command PRPs or SGLs to get the PCI address segments of the command data buffer, retrieve data from the host (if the command is a write command), call req->execute() to execute the command and transfer data to the host (for read commands). - Handle the completions of commands as notified by the ->queue_response() operation of the PCI target controller (nvmet_pci_epf_queue_response() function). Completed commands are added to a list of completed command for their CQ. Each CQ list of completed command is processed using a work item (nvmet_pci_epf_cq_work() function) which posts entries for the completed commands in the CQ memory and raise an IRQ to the host to signal the completion. IRQ coalescing is supported as mandated by the NVMe base specification for PCI controllers. Of note is that completion entries are transmitted to the host using MMIO, after mapping the completion queue memory to the host PCI address space. Unlike for retrieving commands from SQs, DMA is not used as it degrades performance due to the transfer serialization needed (which delays completion entries transmission).The configuration of a NVMe PCI endpoint controller is done usingconfigfs. First the NVMe PCI target controller configuration must bedone to set up a subsystem and a port with the "pci" addr_trtypeattribute. The subsystem can be setup using a file or block devicebacked namespace or using a passthrough NVMe device. After this, thePCI endpoint can be configured and bound to the PCI endpoint controllerto start the NVMe endpoint controller.In order to not overcomplicate this initial implementation of anendpoint PCI target controller driver, protection information is notfor now supported. If the PCI controller port and namespace areconfigured with protection information support, an error will bereturned when the controller is created and initialized when theendpoint function is started. Protection information support will beadded in a follow-up patch series.Using a Rock5B board (Rockchip RK3588 SoC, PCI Gen3x4 endpointcontroller) with a target PCI controller setup with 4 I/O queues and anull_blk block device as a namespace, the maximum performance using fiowas measured at 131 KIOPS for random 4K reads and up to 2.8 GB/Sthroughput. Some data points are:Rnd read, 4KB, QD=1, 1 job : IOPS=16.9k, BW=66.2MiB/s (69.4MB/s)Rnd read, 4KB, QD=32, 1 job : IOPS=78.5k, BW=307MiB/s (322MB/s)Rnd read, 4KB, QD=32, 4 jobs: IOPS=131k, BW=511MiB/s (536MB/s)Seq read, 512KB, QD=32, 1 job : IOPS=5381, BW=2691MiB/s (2821MB/s)The NVMe PCI endpoint target driver is not intended for production use.It is a tool for learning NVMe, exploring existing features and testingimplementations of new NVMe features.Co-developed-by: Rick Wertenbroek Signed-off-by: Damien Le Moal Reviewed-by: Christoph Hellwig Reviewed-by: Manivannan Sadhasivam Tested-by: Manivannan Sadhasivam Reviewed-by: Krzysztof Wilczyński Signed-off-by: Keith Busch List of files: /linux-6.15/drivers/nvme/target/Makefile

5a47c208 - nvmet: support reservation feature

Wed, 06 Nov 2024 07:34:46 +0000

nvmet: support reservation featureThis patch implements the reservation feature, including: 1. reservation register(register, unregister and replace). 2. reservation acquire(acquire, preempt, preempt and abort). 3. reservation release(release and clear). 4. reservation report. 5. set feature and get feature of reservation notify mask. 6. get log page of reservation event.Not supported: 1. persistent reservation through power loss.Test cases: Use nvme-cli and fio to test all implemented sub features: 1. use nvme resv-register to register host a registrant or unregister or replace a new key. 2. use nvme resv-acquire to set host to the holder, and use fio to send read and write io in all reservation type. And also test preempt and "preempt and abort". 3. use nvme resv-report to show all registrants and reservation status. 4. use nvme resv-release to release all registrants. 5. use nvme get-log to get events generated by the preceding operations.In addition, make reservation configurable, one can set ns tosupport reservation before enable ns. The default of resv_enableis false.Signed-off-by: Guixin Liu Reviewed-by: Dmitry Bogdanov Reviewed-by: Christoph Hellwig Tested-by: Chaitanya Kulkarni Reviewed-by: Chaitanya Kulkarni Signed-off-by: Keith Busch List of files: /linux-6.15/drivers/nvme/target/Makefile

649fd414 - nvmet: add debugfs support

Mon, 27 May 2024 05:15:19 +0000

nvmet: add debugfs supportAdd a debugfs hierarchy to display the configured subsystemsand the controllers attached to the subsystems.Suggested-by: Redouane BOUFENGHOUR Signed-off-by: Hannes Reinecke Reviewed-by: Sagi Grimberg Reviewed-by: Chaitanya Kulkarni Signed-off-by: Daniel Wagner Signed-off-by: Keith Busch List of files: /linux-6.15/drivers/nvme/target/Makefile

db1312dd - nvmet: implement basic In-Band Authentication

Mon, 27 Jun 2022 09:52:05 +0000

nvmet: implement basic In-Band AuthenticationImplement NVMe-oF In-Band authentication according to NVMe TPAR 8006.This patch adds three additional configfs entries 'dhchap_key','dhchap_ctrl_key', and 'dhchap_hash' to the 'host' configfs directory.The 'dhchap_key' and 'dhchap_ctrl_key' entries need to be in the ASCIIformat as specified in NVMe Base Specification v2.0 section 8.13.5.8'Secret representation'.'dhchap_hash' defaults to 'hmac(sha256)', and can be written to toswitch to a different HMAC algorithm.Signed-off-by: Hannes Reinecke Reviewed-by: Sagi Grimberg Signed-off-by: Christoph Hellwig Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/target/Makefile

aaf2e048 - nvmet: add ZBD over ZNS backend support

Thu, 10 Jun 2021 01:32:52 +0000

nvmet: add ZBD over ZNS backend supportNVMe TP 4053 – Zoned Namespaces (ZNS) allows host software tocommunicate with a non-volatile memory subsystem using zones for NVMeprotocol-based controllers. NVMeOF already support the ZNS NVMeProtocol compliant devices on the target in the passthru mode. Thereare generic zoned block devices like Shingled Magnetic Recording (SMR)HDDs that are not based on the NVMe protocol.This patch adds ZNS backend support for non-ZNS zoned block devices asNVMeOF targets.This support includes implementing the new command set NVME_CSI_ZNS,adding different command handlers for ZNS command set such as NVMeIdentify Controller, NVMe Identify Namespace, NVMe Zone Append,NVMe Zone Management Send and NVMe Zone Management Receive.With the new command set identifier, we also update the target commandeffects logs to reflect the ZNS compliant commands.Signed-off-by: Chaitanya Kulkarni Reviewed-by: Damien Le Moal Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/target/Makefile

c1fef73f - nvmet: add passthru code to process commands

Fri, 24 Jul 2020 17:25:17 +0000

nvmet: add passthru code to process commandsAdd passthru command handling capability for the NVMeOF target andexport passthru APIs which are used to integrate passthrucode with nvmet-core.The new file passthru.c handles passthru cmd parsing and execution.In the passthru mode, we create a block layer request from the nvmetrequest and map the data on to the block layer request.Admin commands and features are on an allow list as there are a numberof each that don't make too much sense with passthrough. We use anallow list such that new commands can be considered before being blindlypassed through. In both cases, vendor specific commands are alwaysallowed.We also reject reservation IO commands as the underlying device cannotdifferentiate between multiple hosts behind a fabric.Based-on-a-patch-by: Chaitanya Kulkarni Signed-off-by: Logan Gunthorpe Reviewed-by: Keith Busch Reviewed-by: Sagi Grimberg Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/target/Makefile

a5448fdc - nvmet: introduce target-side trace

Wed, 12 Jun 2019 12:45:33 +0000

nvmet: introduce target-side traceThis patch introduces target-side request tracing. As Christophsuggested, the trace would not be in a core or module to avoiddisadvantages like cache miss: http://lists.infradead.org/pipermail/linux-nvme/2019-June/024721.htmlThe target-side trace code is entirely based on the Johannes's trace codefrom the host side. It has lots of codes duplicated, but it would bebetter than having advantages mentioned above.It also traces not only fabrics commands, but also nvme normal commands.Once the codes to be shared gets bigger, then we can make it common assuggsted.This also removed the create_sq and create_cq trace parsing functionsbecause it will be done by the connect fabrics command.Example: echo 1 > /sys/kernel/debug/tracing/event/nvmet/nvmet_req_init/enable echo 1 > /sys/kernel/debug/tracing/event/nvmet/nvmet_req_complete/enable cat /sys/kernel/debug/tracing/traceSigned-off-by: Minwoo Im [hch: fixed the symbol namespace and a an endianess conversion]Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/target/Makefile

872d26a3 - nvmet-tcp: add NVMe over TCP target driver

Tue, 04 Dec 2018 01:52:15 +0000

nvmet-tcp: add NVMe over TCP target driverThis patch implements the TCP transport driver for the NVMe over Fabricstarget stack. This allows exporting NVMe over Fabrics functionality overgood old TCP/IP.The driver implements the TP 8000 of how nvme over fabrics capsules anddata are encapsulated in nvme-tcp pdus and exchaged on top of a TCP bytestream. nvme-tcp header and data digest are supported as well.Signed-off-by: Sagi Grimberg Signed-off-by: Roy Shterman Signed-off-by: Solganik Alexander Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/target/Makefile

d5eff33e - nvmet: add simple file backed ns support

Wed, 23 May 2018 04:34:39 +0000

nvmet: add simple file backed ns supportThis patch adds simple file backed namespace support for NVMeOF target.The new file io-cmd-file.c is responsible for handling the code for I/Ocommands when ns is file backed. Also, we introduce mempools based slowpath using sync I/Os for file backed ns to ensure forward progress underreclaim.The old block device based implementation is moved to io-cmd-bdev.c anduse a "nvmet_bdev_" symbol prefix. The enable/disable calls are alsomove into the respective files.Signed-off-by: Chaitanya Kulkarni [hch: updated changelog, fixed double req->ns lookup in bdev case]Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/target/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvme/target/Makefile

475d0fe7 - nvme-fabrics: Add FC LLDD loopback driver to test FC-NVME

Fri, 02 Dec 2016 08:28:44 +0000

nvme-fabrics: Add FC LLDD loopback driver to test FC-NVMEAdd FC LLDD loopback driver to test FC host and target transport withinnvme-fabricsTo aid in the development and testing of the lower-level api of the FCtransport, this loopback driver has been created to act as if it were aFC hba driver supporting both the host interfaces as well as the targetinterfaces with the nvme FC transport.Signed-off-by: James Smart Reviewed-by: Jay Freyensee Reviewed-by: Johannes Thumshirn Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/target/Makefile

c5343203 - nvme-fabrics: Add target support for FC transport

Fri, 02 Dec 2016 08:28:43 +0000

nvme-fabrics: Add target support for FC transportImplements the FC-NVME T11 definition of how nvme fabric capsules areperformed on an FC fabric. Utilizes a lower-layer API to FC host adaptersto send/receive FC-4 LS operations and perform the FCP transactionsnecessary to perform and FCP IO request for NVME.The T11 definitions for FC-4 Link Services are implemented which createNVMeOF connections. Implements the hooks with nvmet layer to pass NVMEcommands to it for processing and posting of data/response base to thehost via the different connections.Signed-off-by: James Smart Reviewed-by: Jay Freyensee Reviewed-by: Johannes Thumshirn Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/target/Makefile

8f000cac - nvmet-rdma: add a NVMe over Fabrics RDMA target driver

Wed, 06 Jul 2016 12:55:51 +0000

nvmet-rdma: add a NVMe over Fabrics RDMA target driverThis patch implements the RDMA transport for the NVMe over Fabrics target,which allows exporting NVMe over Fabrics functionality over RDMA fabrics(Infiniband, RoCE, iWARP).All NVMe logic is in the generic target and this module just provides asmall glue between it and the generic code in the RDMA subsystem.Signed-off-by: Armen Baloyan ,Signed-off-by: Jay Freyensee Signed-off-by: Ming Lin Signed-off-by: Sagi Grimberg Signed-off-by: Christoph Hellwig Reviewed-by: Steve Wise Tested-by: Steve Wise Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/target/Makefile

3a85a5de - nvme-loop: add a NVMe loopback host driver

Tue, 21 Jun 2016 16:04:21 +0000

nvme-loop: add a NVMe loopback host driverThis patch implements adds nvme-loop which allows to access local devicesexported as NVMe over Fabrics namespaces. This module can be useful foreasy evaluation, testing and also feature experimentation.To createa nvme-loop device you need to configure the NVMe target toexport a loop port (see the nvmetcli documentaton for that) and thenconnect to it using nvme connect-all -t loopwhich requires the very latest nvme-cli version with Fabrics support.Signed-off-by: Jay Freyensee Signed-off-by: Ming Lin Signed-off-by: Sagi Grimberg Signed-off-by: Christoph Hellwig Reviewed-by: Steve Wise Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/target/Makefile

a07b4970 - nvmet: add a generic NVMe target

Tue, 21 Jun 2016 16:04:20 +0000

nvmet: add a generic NVMe targetThis patch introduces a implementation of NVMe subsystems,controllers and discovery service which allows to exportNVMe namespaces across fabrics such as Ethernet, FC etc.The implementation conforms to the NVMe 1.2.1 specificationand interoperates with NVMe over fabrics host implementations.Configuration works using configfs, and is best performed usingthe nvmetcli tool from http://git.infradead.org/users/hch/nvmetcli.git,which also has a detailed explanation of the required steps in theREADME file.Signed-off-by: Armen Baloyan Signed-off-by: Anthony Knapp Signed-off-by: Jay Freyensee Signed-off-by: Ming Lin Signed-off-by: Sagi Grimberg Signed-off-by: Christoph Hellwig Reviewed-by: Steve Wise Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/target/Makefile