Searched refs:NVMe (Results 1 – 25 of 63) sorted by relevance
123
4 tristate "NVMe Target support"20 bool "NVMe Target Passthrough support"32 tristate "NVMe loopback device support"38 to test NVMe host and target side features.43 tristate "NVMe over Fabrics RDMA target support"48 This enables the NVMe RDMA target support, which allows exporting NVMe54 tristate "NVMe over Fabrics FC target driver"59 This enables the NVMe FC target support, which allows exporting NVMe73 to test NVMe-FC transport interfaces.78 tristate "NVMe over Fabrics TCP target support"[all …]
6 What is NVMe9 NVM Express (NVMe) is a register level interface that allows host software to26 There is an NVMe uclass driver (driver name "nvme"), an NVMe host controller31 is triggered by the NVMe uclass driver and the actual work is done in the NVMe36 It only support basic block read/write functions in the NVMe driver.40 CONFIG_NVME Enable NVMe device support41 CONFIG_CMD_NVME Enable basic NVMe commands46 be executed for all NVMe hard disks attached to the NVMe controller to be49 To list all of the NVMe hard disks, try:78 Testing NVMe with QEMU x86[all …]
19 bool "NVMe multipath support"22 This option enables support for multipath access to NVMe24 /dev/nvmeXnY device will show up for each NVMe namespace,28 bool "NVMe verbose error reporting"31 This option enables verbose reporting for NVMe errors. The36 bool "NVMe hardware monitoring"39 This provides support for NVMe hardware monitoring. If enabled,53 This provides support for the NVMe over Fabrics protocol using69 This provides support for the NVMe over Fabrics protocol using71 exported using the NVMe protocol set.[all …]
4 Linux NVMe feature and and quirk policy8 Linux NVMe driver and what is not.16 The Linux NVMe host driver in drivers/nvme/host/ supports devices17 implementing the NVM Express (NVMe) family of specifications, which20 - the NVMe Base specification23 - the NVMe Management Interface specification25 See https://nvmexpress.org/developers/ for the NVMe specifications.36 maintainability of the NVMe host driver.38 Any feature implemented in the Linux NVMe host driver must support the41 1. The feature is specified in a release version of an official NVMe[all …]
1 ### NVMe-MI over SMBus9 Currently, OpenBMC does not support NVMe drive information. NVMe-MI10 specification defines a command that can read the NVMe drive information via11 SMBus directly. The NVMe drive can provide its information or status, like13 monitor NVMe drives so appropriate action can be taken.17 NVMe-MI specification defines a command called47 each NVMe sensor: "/xyz/openbmc_project/sensors/temperature/nvme0",173 ##### Add SEL related to NVMe186 NVMe-MI specification defines multiple commands that can communicate with NVMe197 SMBus directly is much simpler than NVMe-MI over MCTP protocol.[all …]
23 - description: NVMe and NVMMU registers38 - description: power domain for the NVMe controller.39 - description: power domain for the first PCIe bus connecting the NVMe42 connecting the NVMe controller to the storage modules.
2 DESCRIPTION = "This package contains the command line interface to the NVMe \11 # nvmet service will start and stop the NVMe Target configuration on boot and12 # shutdown from a saved NVMe Target configuration in the /etc/nvmet/config.json
1 SUMMARY = "NVMe Drive Manager"2 DESCRIPTION = "Daemon to monitor and report the status of NVMe drives"
46 For example, in the NVMe Target Copy Offload implementation:48 * The NVMe PCI driver is both a client, provider and orchestrator54 can DMA directly to the memory exposed by the NVMe device.55 * The NVMe Target driver (nvmet) can orchestrate the data from the RNIC56 to the P2P memory (CMB) and then to the NVMe device (and vice versa).62 then the NVMe Target could use the RNIC's memory instead of the CMB63 in cases where the NVMe cards in use do not have CMB support.96 example, the NVMe Target driver creates a list including the namespace
16 NVMe, enumerator61 {Protocol::NVMe, "NVMe"},
8 NVMe/MMC drives and resulted in the swap partition being used without34 + NVMe/MMC drives and resulted in the swap partition being used without52 + # Correctly handle NVMe/MMC drives, as well as any similar physical
1 # Enable NVMe flash storage support
3 * Google Herobrine dts fragment for NVMe SKUs
15 model = "Google Zombie with LTE and NVMe";
15 model = "Google Zombie with NVMe";
58 (2) PCI device pass-through: While NVMe ZNS emulation is available for testing60 the NVMe ZNS device to the guest, use VFIO PCI pass the entire NVMe PCI adapter
2 NVMe Emulation5 QEMU provides NVMe emulation through the ``nvme``, ``nvme-ns`` and10 * `Adding NVMe Devices`_, `additional namespaces`_ and `NVM subsystems`_.15 Adding NVMe Devices21 The QEMU emulated NVMe controller implements version 1.4 of the NVM Express29 The simplest way to attach an NVMe controller on the QEMU PCI bus is to add the305 by the NVMe device. Virtual function controllers will not report SR-IOV.336 The minimum steps required to configure a functional NVMe secondary367 * bind the NVMe driver to the VF
2 Description=NVMe Sensor
11 It supports basic functions of NVMe (read/write).
85 Intel NVMe drives contain two cores on the physical device.113 unstriped on top of Intel NVMe device that has 2 cores121 There will now be two devices that expose Intel NVMe core 0 and 1
4 not limited to Ethernet, NVMe over Fabrics, etc.
2 Description=NVMe management
3 libnvme provides type definitions for NVMe specification structures, \
1438 // Remove NVMe temperature objects from cache when they are removed from
1 SUMMARY = "NVMe management command line interface"