- 20 Dec, 2023 10 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
... a chance to take memory from the old
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
- 18 Dec, 2023 2 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
-
- 17 Dec, 2023 2 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
-
- 15 Dec, 2023 3 commits
-
-
Nils Goroll authored
otherwise we would hold onto log blocks for a long time, possibly until the next ref'ing flush. This could cause lock ups due to no memory being available. This is considered a major contribution towards fixing the lockup issues documented in #41
-
Nils Goroll authored
-
Nils Goroll authored
-
- 14 Dec, 2023 12 commits
-
-
Nils Goroll authored
kick the logwatcher first before potentially running into a synchronous flush.
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
Related to #45
-
- 13 Dec, 2023 11 commits
-
-
Nils Goroll authored
The oh-so-smart idea from 39c2568e was pretty dumb after all: While testing with the low RAM config (16MB on 10GB), a lockop was found with only ~45% of RAM occupied. The reason for the lockup was the un-crammed 64KB (16bits) request for a regionlist with priority 4, which was blocking all other requests. So: No, trying to allocate something "just in case" is never a good idea.
-
Nils Goroll authored
-
Nils Goroll authored
It should allow log transactions to complete first
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
A pool tries to always have allocations ready. There are two buddy_reqs, and when one is depleted, allocations are taken from the other, while the empty reqs are being filled again.
-
Nils Goroll authored
such that the test can easily be run with 2>/dev/null if the dbg output is of no interest.
-
Nils Goroll authored
-
Nils Goroll authored
-