summaryrefslogtreecommitdiffstats
path: root/cmake
diff options
context:
space:
mode:
authorSimon Rettberg2020-10-29 17:23:03 +0100
committerSimon Rettberg2020-10-29 17:23:03 +0100
commit1dbcfdd00ae69ecdb16256de816c4030646223dc (patch)
tree9a6878b39afc2ea7fbc31e511b499e02c11c14f4 /cmake
parent[BUILD] do not print verbose CMake messages in unsupported CMake versions (diff)
downloaddnbd3-1dbcfdd00ae69ecdb16256de816c4030646223dc.tar.gz
dnbd3-1dbcfdd00ae69ecdb16256de816c4030646223dc.tar.xz
dnbd3-1dbcfdd00ae69ecdb16256de816c4030646223dc.zip
[SERVER] Update nextSave timestamp at start of function
saveLoadAllCacheMaps() is called frequently, and a 'full' run can take some time. If we only update the nextSave timestamp when we're done, we might already have a concurrent call to the function, which will also do a 'full' run, since the timestamp is not updated yet. This doesn't break anything, but leads to even more disk activity, which is probably already high, given that the previous run is not done yet.
Diffstat (limited to 'cmake')
0 files changed, 0 insertions, 0 deletions