summaryrefslogtreecommitdiffstats
path: root/clang
diff options
context:
space:
mode:
authorPeter Collingbourne <peter@pcc.me.uk>2017-06-23 17:05:03 +0000
committerPeter Collingbourne <peter@pcc.me.uk>2017-06-23 17:05:03 +0000
commit8d292233869a68a6a6e826924519e552a404b7f5 (patch)
tree080ff32072ff8e2be67c44e847dba9b4944f6a05 /clang
parent38a02daea4f1fb155fe407b4772cfc9eaaf4230e (diff)
downloadbcm5719-llvm-8d292233869a68a6a6e826924519e552a404b7f5.tar.gz
bcm5719-llvm-8d292233869a68a6a6e826924519e552a404b7f5.zip
Add a ThinLTO cache policy for controlling the maximum cache size in bytes.
This is useful when an upper limit on the cache size needs to be controlled independently of the amount of the amount of free space. One use case is a machine with a large number of cache directories (e.g. a buildbot slave hosting a large number of independent build jobs). By imposing an upper size limit on each cache directory, users can more easily estimate the server's capacity. Differential Revision: https://reviews.llvm.org/D34547 llvm-svn: 306126
Diffstat (limited to 'clang')
-rw-r--r--clang/docs/ThinLTO.rst12
1 files changed, 12 insertions, 0 deletions
diff --git a/clang/docs/ThinLTO.rst b/clang/docs/ThinLTO.rst
index 71a23380efb..31fff51a61e 100644
--- a/clang/docs/ThinLTO.rst
+++ b/clang/docs/ThinLTO.rst
@@ -146,6 +146,18 @@ Possible key-value pairs are:
disk space. A value over 100 is invalid. A value of 0 disables the percentage
size-based pruning. The default is 75%.
+- ``cache_size_bytes=X``, ``cache_size_bytes=Xk``, ``cache_size_bytes=Xm``,
+ ``cache_size_bytes=Xg``:
+ Sets the maximum size for the cache directory to ``X`` bytes (or KB, MB,
+ GB respectively). A value over the amount of available space on the disk
+ will be reduced to the amount of available space. A value of 0 disables
+ the byte size-based pruning. The default is no byte size-based pruning.
+
+ Note that ThinLTO will apply both size-based pruning policies simultaneously,
+ and changing one does not affect the other. For example, a policy of
+ ``cache_size_bytes=1g`` on its own will cause both the 1GB and default 75%
+ policies to be applied unless the default ``cache_size`` is overridden.
+
- ``prune_after=Xs``, ``prune_after=Xm``, ``prune_after=Xh``: Sets the
expiration time for cache files to ``X`` seconds (or minutes, hours
respectively). When a file hasn't been accessed for ``prune_after`` seconds,
OpenPOWER on IntegriCloud