Changes between Version 3 and Version 4 of rfc26_blockcache


Ignore:
Timestamp:
Sep 25, 2012, 4:06:30 AM (12 years ago)
Author:
Even Rouault
Comment:

Fix wrong ticket references

Legend:

Unmodified
Added
Removed
Modified

  • rfc26_blockcache

    v3 v4  
    1515depending on the raster size, which would optimize between the performance and the memory utilization in all cases.
    1616
    17 This RFC would also address the multithreading issues discovered in #3324 and #3325.
     17This RFC would also address the multithreading issues discovered in #3224 and #3225.
    1818
    1919
    … …  
    3737
    3838Protecting the band level cache from the access of multiple threads may happen by using a per-band mutex of the
    39 raster band, however using this second mutex may easily lead to deadlock situations as pointed out in #3324. To avoid this situation it would be much
     39raster band, however using this second mutex may easily lead to deadlock situations as pointed out in #3224. To avoid this situation it would be much
    4040safer to use hRBMutex to protect the simoultaneous access to the per-band cache as well. In most cases when accessing the per-band
    4141cache, hRBMutex is also involved in various operations (like GDALRasterBlock:Touch, GDALRasterBlock:Internalize,