[Tile-serving] [mod_tile] Don't use apr_global_mutex to guard storage backend initialisation (#28)

apmon notifications at github.com
Thu May 23 03:17:12 UTC 2013

Commit 2c538916be4f8dff28181ea5a47d65d84b4b2a03 introduced locking around memory allocation for an array containing pointers to the storage backends, as apache's memory pool functions aren't thread safe. It used apr_global_mutex, but I think apr_global_mutex not only synchronizes between threads, but also between process which isn't necessary for the storage backend memory allocation. Instead presumably apr_thread_mutex is what we want.

I need to verify this before committing the change, hence this reminder ticket.

Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20130522/0e170cb0/attachment.html>

More information about the Tile-serving mailing list