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
author Chorazewicz, Igor <[email protected]> 1632834667 +0200
committer Daniel Byrne <[email protected]> 1671070203 -0800
Initial multi-tier support implementation
Extend CompressedPtr to work with multiple tiers
Now it's size is 8 bytes intead of 4.
Original CompressedPtr stored only some offset with a memory Allocator.
For multi-tier implementation, this is not enough. We must also store
tierId and when uncompressing, select a proper allocator.
An alternative could be to just resign from CompressedPtr but they
are leveraged to allow the cache to be mapped to different addresses on shared memory.
Changing CompressedPtr impacted CacheItem size - it increased from 32 to 44 bytes.
Implemented async Item movement between tiers (with corrected
behaivour of tryEvictToNextMemoryTier).
Fix ReaperSkippingSlabTraversalWhileSlabReleasing test
The issue was caused by incorrect behaviour of the
CacheAllocator<CacheTrait>::tryEvictToNextMemoryTier method in case the
evicted item is expired. We cannot simply return a handle to it, but we need
to remove it from the access container and MM container.
Enable workarounds in tests
Add basic multi-tier test
Set correct size for each memory tier
Do not compensate for rounding error when calculating tier sizes (pmem#43)
Compensation results in ratios being different than originially specified.
Fixed total cache size in CacheMemoryStats (pmem#38)
Return a sum of sizes of each tier instead of just 1st tier's size.
Issue75 rebased (pmem#88)
* pmem#75: Use actual tier sizes (rounded down to slab size and decreased by header size) when creating new memory pools
* Added getPoolSize method to calculate combined pool size for all tiers; added pool size validation to tests
* Explicitly specified type for totalCacheSize to avoid overflow
* Minor test change
* Reworked tests
* Minor change
* Deleted redundant tests
* Deleted unused constant
* First set of changes to cache configuration API to enable multi-tier caches (facebook#138)
Summary:
These changes introduce per-tier cache configuration required to implement features discussed here: facebook#102. These specific changes enable single DRAM tier configs only which are compatible with the current version of cachelib. Configuration API will be expanded as multi-tier changes in other parts of the library are introduced.
Pull Request resolved: facebook#138
Reviewed By: therealgymmy
Differential Revision: D36189766
Pulled By: jiayuebao
fbshipit-source-id: 947aa0cd800ea6accffc1b7b6b0c9693aa7fc0a5
Co-authored-by: Victoria McGrath <[email protected]>
Fix eviction flow and removeCb calls
Without this fix removeCb called even in case when Item is moved between
tiers.
Fix issue with "Destorying an unresolved handle"
The issue happened when ReadHandleImpl ctor needs to destroy
waitContext_ because addWaitContextForMovingItem() returns false.
So before destroying waitContext_ we are calling discard method to
notify ~ItemWaitContext() that Item is ready.
Fix slab release code
Get tier id of item before calling any function on allocator
(which needs the tierID).
0 commit comments