e5f6a99b61
Previously, the shared buffer pools were allocated on the nvmf controllers. When a new connection was established, the CONNECT command needs a 4k buffer, but we didn't know which nvmf controller it belonged to until after the CONNECT command completed. So there was a special case for CONNECT that used in capsule data buffers instead. Now, the buffer pool is global and always available. We can just use that always, with no more special cases. This has the additional nice side effect of allowing users to run the target with no in capsule data buffers allocated at all. Change-Id: I974289f646947651c58d65cf898571d80e9dee9b Signed-off-by: Ben Walker <benjamin.walker@intel.com> Reviewed-on: https://review.gerrithub.io/374360 Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> |
||
|---|---|---|
| .. | ||
| iscsi.conf.in | ||
| nvmf.conf.in | ||
| rocksdb.conf.in | ||
| vhost.conf.in | ||