ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
861e78bf48
Spdk/test/nvmf/nvmf.conf

16 lines
245 B
Plaintext
Raw Normal View History

nvmf: add automated fio and mkfs tests Change-Id: I499ae29155b8f053babf18750cecb5c8d210d59c Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-06-07 15:49:44 +00:00
[Global]
Comment "Global section"
LogFacility "local7"
[Nvmf]
nvmf: Rename MaxConnectionsPerSession to MaxQueuesPerSession Change-Id: I9891f9ed481b93312152c2a59f4263003167f1d6 Signed-off-by: Ben Walker <benjamin.walker@intel.com>
2016-07-18 22:17:32 +00:00
MaxQueuesPerSession 4
nvmf: add automated fio and mkfs tests Change-Id: I499ae29155b8f053babf18750cecb5c8d210d59c Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-06-07 15:49:44 +00:00
[Nvme]
ClaimAllDevices Yes
UnbindFromKernel Yes
nvmf: Rename SubsystemGroup to Susbystem in conf file The section is really defining a subsystem as defined by the NVMf specification. There does not appear to be any need for a group of subsystems. This change only updates the configuration file. It does not remove all references to a subsystem group from the code. Change-Id: I38e62735a5ac924dcafacb3c9a332a103d751d4a Signed-off-by: Ben Walker <benjamin.walker@intel.com>
2016-06-08 18:22:36 +00:00
[Subsystem1]
nvmf: Remove NodeBase. Each Subsystem now defines its own NQN This is just extra complication for no real benefit. Change-Id: I528af98e799d0641e753390fe35ff561fa3d7d76 Signed-off-by: Ben Walker <benjamin.walker@intel.com>
2016-07-11 22:22:03 +00:00
NQN "nqn.2016-06.io.spdk:cnode1"
nvmf: Remove host.[ch] and port.[ch] These can be simplified and merged into the subsystem. Remove the concept of mappings from subsystems and replace it with a list of hosts and ports. The host is optional - not specifying a host means any host can connect. Change-Id: Ib3786acb40a34b7e10935af55f4b6756d40cc906 Signed-off-by: Ben Walker <benjamin.walker@intel.com>
2016-07-15 21:16:59 +00:00
Listen RDMA 192.168.100.8:4420
nvmf: only allow one Controller per Subsystem Multiple NVMe controllers within a subsystem does not work correctly, since we would need to virtualize the controller data, namespace IDs, and so on. For now, only allow pass-through mapping of a single NVMe controller per subsystem. Change-Id: Ib2d3576d2856c46a086f38eb6bec56f3e7a73575 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-06-30 17:36:12 +00:00
Controller Nvme0
Reference in New Issue Copy Permalink