Shared Persistent Heap Data Environment Manual
1.1.0
|
A future improvement would specify a Near Window that would restrict near allocations to be from a power of two sub-block of the containing Compound Heap. This could be used with large pages to restrict spill allocations to be from the same large page. For example if the Simple Heaps where allocated as 4K blocks but the physical Page size was 64K or 16M.
A lock Free Compound Heap to compliment the SPH Lock Free Heap implementation of sphlockfreeheap.h would be a useful addition to the SAS/SPH runtime.
In a future implementation the intent is to extend SAS Locks to support Write Intent locks. Intent Locks would allow the holder to gain a shared lock that can be upgraded to exclusive write lock later, if needed. A Intent lock allows current holders of read locks to continue, but prevents new read locks from being granted. New read locks are held (not granted) until the corresponding Intent Lock or upgraded Write Lock is released (unlockd).
Need a API to return the PIDs associated with held locks. This will be needed to recover from hung or crashed processes.