372df452a4
Some modules rely on accurate memory buffer counts. For example, bdev checks that all of its buffer pools are back to original capacity during spdk_bdev_finish(). So flesh out the mempool implementation in test_env.c to keep accurate counts of the number of buffers "available" in the test mempool. Note that test_env is only designed for unit tests, so this functionality is not multi-thread safe. Still allow for NULL mempool pointers and just default to old behavior in that case - some unit tests such as the blobfs cache tree tests still rely on that behavior. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I1d0ab49e16741c92d777d76f35e60271e4ad943a Reviewed-on: https://review.gerrithub.io/377969 Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> |
||
|---|---|---|
| .. | ||
| bdev | ||
| blobfs | ||
| env | ||
| event | ||
| ioat | ||
| json | ||
| nvme | ||
| Makefile | ||
| test_env.c | ||