Lines Matching full:subsystem

19 subsystem using a port. The port transfer type must be configured to be
20 "pci". The subsystem can be configured to have namespaces backed by regular
70    resets, the controller capability NSSR bit (NVM Subsystem Reset Supported)
154 as a subsystem namespace can be used.
181 subsystem and port must be defined. Second, the NVMe PCI endpoint device must
182 be setup and bound to the subsystem and port created.
184 Creating a NVMe Subsystem and Port
187 Details about how to configure a NVMe target subsystem and port are outside the
189 and subsystem with a single namespace backed by a null_blk device.
210 Now, create a subsystem and a port that we will use to create a PCI target
222 Next, create and enable the subsystem namespace using the null_blk block
229 Finally, create the target port and link it to the subsystem::
240 With the NVMe target subsystem and port ready for use, the NVMe PCI endpoint
259 be automatically set to the same value as the NVMe target subsystem vendor
271 Next, let's bind our endpoint device with the target subsystem and port that we
291         nvmet: adding nsid 1 to subsystem nvmepf.0.nqn
293 …nvmet: Created nvm controller 1 for subsystem nvmepf.0.nqn for NQN nqn.2014-08.org.nvmexpress:uuid…
345 vendorid           Ignored (the vendor id of the NVMe target subsystem is used)
352 subsys_vendor_id   Ignored (the subsystem vendor id of the NVMe target subsystem
367 subsysnqn          The NQN of the target subsystem to use