iproto: use xmempool_alloc for connection and message allocations
The mempools are unlimited so allocations from them never fail. Even if we decide to add a hard limit some day, it's better to do it somewhere in one place to simplify testing so the dropped code isn't going to be needed. NO_DOC=code cleanup NO_TEST=code cleanup NO_CHANGELOG=code cleanup
Showing
- src/box/iproto.cc 16 additions, 74 deletionssrc/box/iproto.cc
- src/lib/core/evio.c 2 additions, 6 deletionssrc/lib/core/evio.c
- src/lib/core/evio.h 1 addition, 1 deletionsrc/lib/core/evio.h
- test/box/errinj.result 0 additions, 98 deletionstest/box/errinj.result
- test/box/errinj.test.lua 0 additions, 44 deletionstest/box/errinj.test.lua
Loading
Please register or sign in to comment