aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2014-04-03 12:06:44 -0400
committerNick Mathewson <nickm@torproject.org>2014-04-24 10:26:14 -0400
commit17ecd04fde2fd98b0cca3afb251b7173e22d3f42 (patch)
tree5e353b035c9506a47021c760b1dbe0a1b3ebafee /changes
parentaca05fc5c08d6296c4f93850a0256bfd96890b18 (diff)
downloadtor-17ecd04fde2fd98b0cca3afb251b7173e22d3f42.tar
tor-17ecd04fde2fd98b0cca3afb251b7173e22d3f42.tar.gz
Change the logic for the default for MaxMemInQueues
If we can't detect the physical memory, the new default is 8 GB on 64-bit architectures, and 1 GB on 32-bit architectures. If we *can* detect the physical memory, the new default is CLAMP(256 MB, phys_mem * 0.75, MAX_DFLT) where MAX_DFLT is 8 GB on 64-bit architectures and 2 GB on 32-bit architectures. You can still override the default by hand. The logic here is simply trying to choose a lower default value on systems with less than 12 GB of physical RAM.
Diffstat (limited to 'changes')
-rw-r--r--changes/bug113967
1 files changed, 7 insertions, 0 deletions
diff --git a/changes/bug11396 b/changes/bug11396
new file mode 100644
index 000000000..af94be04f
--- /dev/null
+++ b/changes/bug11396
@@ -0,0 +1,7 @@
+ o Minor features (security):
+
+ - If you don't specify MaxMemInQueues yourself, Tor now tries to
+ pick a good value based on your total system memory. Previously,
+ the default was always 8 GB. You can still override the default by
+ setting MaxMemInQueues yourself. Resolves ticket 11396.
+