aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
Diffstat (limited to 'changes')
-rw-r--r--changes/bug1139611
-rw-r--r--changes/bug1155315
2 files changed, 0 insertions, 26 deletions
diff --git a/changes/bug11396 b/changes/bug11396
deleted file mode 100644
index fd263291d..000000000
--- a/changes/bug11396
+++ /dev/null
@@ -1,11 +0,0 @@
- 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.
-
- o Minor features (controller):
- - Because of the fix for ticket 11396, the real limit for memory
- usage may no longer match the configured MaxMemInQueues value.
- The real limit is now exposed via GETINFO limits/max-mem-in-queues.
diff --git a/changes/bug11553 b/changes/bug11553
deleted file mode 100644
index ed30ce985..000000000
--- a/changes/bug11553
+++ /dev/null
@@ -1,15 +0,0 @@
- o Minor features:
- - When we run out of usable circuit IDs on a channel, log only one
- warning for the whole channel, and include a description of
- how many circuits there were on the channel. Fix for part of ticket
- #11553.
-
-
- o Major features (performance):
- - Avoid wasting cycles looking for usable circuit IDs. Previously,
- when allocating a new circuit ID, we would in the worst case do a
- linear scan over the entire possible range of circuit IDs before
- deciding that we had exhausted our possibilities. Now, we
- try 64 circuit IDs at random before deciding that we probably
- won't succeed. Fix for a possible root cause of ticket
- #11553.