osrm-backend/include
Michael Krasnyk 7753845f5c Make thread-locked access to stxxl containers
From stxxl FAQ: "you should not share a data structure between
threads (without implementing proper locking yourself)."
The access to name_char_data can be implicitly parallelized
if _GLIBCXX_PARALLEL is defined and invalidate local-thread iterators.
2016-10-25 10:03:26 -07:00
..
contractor Rename increasingly inaccuratly named distance member of QueryEdge to weight 2016-10-21 21:00:02 +02:00
engine Rename increasingly inaccuratly named distance member of QueryEdge to weight 2016-10-21 21:00:02 +02:00
extractor Make thread-locked access to stxxl containers 2016-10-25 10:03:26 -07:00
osrm Makes the OSRM interface threadsafe. 2016-10-04 09:32:22 +02:00
server Use mmap instead of read - it's a lot faster here. 2016-06-27 17:24:30 -07:00
storage Store node ID's and weights separately in CompressedEdgeContainer 2016-10-20 11:32:28 -07:00
util Rename increasingly inaccuratly named distance member of QueryEdge to weight 2016-10-21 21:00:02 +02:00