Daniel Verkamp a9df326a0e 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-07-07 15:09:30 -07:00
..
conf	conf: Add configuration file iteration functions	2016-05-13 09:51:37 -07:00
cunit	cunit: add test result JSON formatting	2016-05-12 15:42:09 -07:00
event	event: Add dpdk framework start function into event.	2016-07-01 10:07:42 -07:00
ioat	build: wrap $(CURDIR) relative paths in $(abspath)	2016-05-09 13:56:07 -07:00
json	json: fix spdk_json_write_val with nested objects	2016-05-11 10:43:02 -07:00
jsonrpc	jsonrpc: add JSON-RPC 2.0 library	2016-05-23 10:28:58 -07:00
log	log: allow setting all trace flags at once	2016-05-12 09:47:57 -07:00
memory	vtophys: fix usermode address range check	2016-06-22 16:41:29 -07:00
nvme	nvme: combine CAP register into one 64-bit union	2016-07-07 13:52:16 -07:00
nvmf	nvmf: only allow one Controller per Subsystem	2016-07-07 15:09:30 -07:00
rpc	rpc: Add an RPC subsystem	2016-06-22 15:45:50 -07:00
trace	trace: validate group IDs	2016-05-24 09:53:19 -07:00
util	build: wrap $(CURDIR) relative paths in $(abspath)	2016-05-09 13:56:07 -07:00
Makefile	rpc: Add an RPC subsystem	2016-06-22 15:45:50 -07:00