@return whether pool rebalancing is enabled

Returns true if the state was already initialized and set up. False if we state was not present.

return the index of this allocation in the BucketStorage

TODO(sathya) clean up this api by making this part of the find api implementation.

Detaches the real device from the mock object

Remove the value for a key. Returns true is successful

Clear the buffer

Resize the compact cache to its new, desired size

increase val if no overflow, otherwise do nothing

sets the next in the hash chain to the passed in value.

Configure the max key size for Navy

Notify the workload generator that the nvm cache has already warmed up.

record the item handle. Upon destruction we will wake up the waiters and pass a clone of the handle to the callBack. By default we pass a null handle

Insert a key->value mapping into the pool. Returns true if the insertion was successful, false otherwise. This will overwrite existing data, and sets

sharding is based on each mutex boundary

To force the compiler to NOT optimize away the store/load when user supplies void* and we need to read it in 32bit chunks. The compiler should be able

To force the compiler to NOT optimize away the store/load when user supplies void* and we need to read it in 64bit chunks. The compiler should be able

test that the behavior of could exist works as expected when one of the engine is a no-op engine.

Throw readable exception if the key is invalid.

* IOOp */