summaryrefslogtreecommitdiff
path: root/indra/llfilesystem/lldiskcache.h
diff options
context:
space:
mode:
authorNat Goodspeed <nat@lindenlab.com>2021-05-17 10:24:27 -0400
committerNat Goodspeed <nat@lindenlab.com>2021-05-17 10:24:27 -0400
commit87faf258911f5d23416500ff632050ce05b30e3e (patch)
tree120f10eb9097ed75d7cc7da95365670c1fb5b882 /indra/llfilesystem/lldiskcache.h
parent89cf988aaf0de402641cd945e7e9ad5292bc78d6 (diff)
SL-15200: Explain why purge() is called on another thread.
Also add Ansariel's explanation for why interaction through the filesystem itself should be safe.
Diffstat (limited to 'indra/llfilesystem/lldiskcache.h')
-rw-r--r--indra/llfilesystem/lldiskcache.h4
1 files changed, 4 insertions, 0 deletions
diff --git a/indra/llfilesystem/lldiskcache.h b/indra/llfilesystem/lldiskcache.h
index 7c5b798f7e..268fe92bcc 100644
--- a/indra/llfilesystem/lldiskcache.h
+++ b/indra/llfilesystem/lldiskcache.h
@@ -121,6 +121,10 @@ class LLDiskCache :
*
* WARNING: purge() is called by LLPurgeDiskCacheThread. As such it must
* NOT touch any LLDiskCache data without introducing and locking a mutex!
+ *
+ * Purging the disk cache involves nontrivial work on the viewer's
+ * filesystem. If called on the main thread, this causes a noticeable
+ * freeze.
*/
void purge();