You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1711: [ BUGFIX ] Fabrics connect timeouts r=tiagolobocastro a=tiagolobocastro
Reactor block_on may prevent spdk thread messages from running and therefore this can lead to starvation of messages pulled from the thread ring, which are not polled during the block_on.
There are still a few uses remaining, most during init setup, so mostly harmless, though the Nexus Bdev destruction which runs on blocking code, does still contain a block_on.
---
fix(nvmf/target): remove usage of block_on
Split creating from starting the subsystem.
This way we can start the subsystem in master reactor, and then move
to the next spdk subsystem.
Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
---
fix(nexus-child/unplug): remove usage of block_on
Initially this block_on was added because the remove callback was running in blocking
fashion, but this has since changed and unplug is actually called from async context.
As such, we don't need the block_on and simply call the async code directly.
Also, simplify complete notification, as we can simply close the sender.
Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
---
fix(nvmx/qpair): return errno with absolute value
Otherwise a returned negative value translates into an unknown Errno.
Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
---
feat: allow custom fabrics connect timeout
Allows passing this via env NVMF_FABRICS_CONNECT_TIMEOUT.
Also defaults it to 3s for now, rather than 500ms.
Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
Co-authored-by: Tiago Castro <tiagolobocastro@gmail.com>
0 commit comments