efca92b85b
The generic NVMe library controller initialization process already handles enabling the controller; the RDMA transport should not need to set EN itself. For now, the discovery controller is cheating and not using the normal initialization process, so move the EN = 1 hack to the discovery controller bringup until it is overhauled to use the full nvme_ctrlr_process_init() path. The previous code where CC.EN was set to 1 before going through the controller init process would cause an EN = 1 to EN = 0 transition, which triggers a controller level reset. This change stops us from causing a reset during the controller startup sequence, which is defined by the NVMe over Fabrics spec as terminating the host/controller association (breaking the connection). Our NVMe over Fabrics target does not yet implement this correctly, but we should still do the right thing in preparation for a full reset implementation. This patch also reverts the NVMe over Fabrics target reset handling hack that was added as part of the NVMe over Fabrics host commit to its previous state of just printing an error message. Change-Id: I0aedd73dfd2dd1168e7b13b79575cc387737d4f0 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> |
||
|---|---|---|
| .. | ||
| direct.c | ||
| Makefile | ||
| nvmf_internal.h | ||
| nvmf.c | ||
| rdma.c | ||
| request.c | ||
| request.h | ||
| session.c | ||
| session.h | ||
| subsystem.c | ||
| subsystem.h | ||
| transport.c | ||
| transport.h | ||
| virtual.c | ||