If the purpose of multithreading is performance, a mutex will ruin that performance. Opening different datasets solves that already.
For writing, allowing different synchronous writers is... scary. On Mon, 3 Jun 2024, 16:12 Chris Toney via gdal-dev, < gdal-dev@lists.osgeo.org> wrote: > Hi Andrew, > Some related comments and links are in: > https://github.com/OSGeo/gdal/issues/9091 > > Chris > > On Mon, Jun 3, 2024 at 7:44 AM Andrew Bell via gdal-dev < > gdal-dev@lists.osgeo.org> wrote: > >> Hi, >> >> I am aware that there isn't thread-safe raster access with the current >> GDAL interface for various reasons. Given the state of processors, I was >> wondering if it would be valuable to take a look at providing the ability >> to do Raster I/O (at least reads) in a thread-safe way. This could be done >> through a new set of API calls or perhaps by modifications to what >> currently exists -- I don't know what makes sense at this point. I would be >> happy to spend some time looking at this if there is interest, but I would >> also like to learn from existing experience as to what kinds of things that >> I'm surely not considering would have to be dealt with. >> >> Thanks, >> >> -- >> Andrew Bell >> andrew.bell...@gmail.com >> _______________________________________________ >> gdal-dev mailing list >> gdal-dev@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/gdal-dev >> > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
