Changes between Initial Version and Version 4 of Ticket #3689


Ignore:
Timestamp:
Jul 18, 2010, 3:53:43 AM (14 years ago)
Author:
Even Rouault
Comment:

r20095 /trunk/gdal/gcore/gdalrasterblock.cpp: GDALSetCacheMax64() / GDALGetCacheMax64() : remove the restriction to 2GB on 32bit OS. Some configuration of Linux and Windows allow a value between 2GB and 4GB. It is up to the user to specify a sensible value (#3689)

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3689

    • Property Status new → closed
    • Property Resolution → fixed

  • Ticket #3689 – Description

    initial v4  
    1 The attached patch changes the internal type of the max cache size to GIntBig to allow more than 2GB for GDAL cache. It introduces the GDALSetCacheMax64(), GDALGetCacheMax64() and GDALGetCacheUsed64() API. Old 32 bit API are preserved for backward compatibility. Old 32 bit API warn the user if they must be truncated the returned value (GetCacheMax() and GetCacheUsed()). GDALSetCacheMax64() warns when the user tries to pass a value greater than the max int on a 32bit GDAL build.
     1The attached patch changes the internal type of the max cache size to GIntBig to allow more than 2GB for GDAL cache. It introduces the GDALSetCacheMax64(), GDALGetCacheMax64() and GDALGetCacheUsed64() API. Old 32 bit API are preserved for backward compatibility. Old 32 bit API warn the user if they must be truncated the returned value (GetCacheMax() and GetCacheUsed()).
    22
    3 Any objection ?
     3On 32bit builds of GDAL, GDALSetCacheMax64() will *NOT* warn if the user tries to pass a value greater than the maximum amount of memory that can be addressed. (This is a change w.r.t. the initial implementation since 32bit OS depending on their configuration can allow a process to allocate between 2 and 4 GB)