diff options
| author | Neale Ferguson <neale@sinenomine.net> | 2022-09-02 10:27:56 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-09-02 10:27:56 +0300 |
| commit | 0c32ff765c55eecd0d78336d5805421c4bc661de (patch) | |
| tree | 550399a0607cbb6e361523137b0beb5f1d0c21fe /man | |
| parent | 5567e4785dee8b02ea5ffa2ac9d39b1cb04ecbf4 (diff) | |
CGroup fix to match coreCLR PR 64128 (#21503)
Update memory usage calculation in line with comments made in [coreCLR cgroup PR](https://github.com/dotnet/runtime/pull/64128).
The other significant change is the use of `sysconf(_SC_PHYS_PAGES)`. In the earlier version of this code I had used `sysconf(_SC_AVPHYS_PAGES)`. The latter is often significantly smaller (by an order of magnitude) to the former meaning that the value returned may be quite low. However, I am unsure whether mono already takes this into account. For example, running in with no-cgroup restrictions on a 16G virtual machine would report a `_SC_AVPHYS_PAGES` value of 79138 pages resulting in a memory value of 324149248 bytes (309MB) being returned. When setting cgroup constraints:
```
systemd-run -q --scope -p CPUQuota=400% -p MemoryLimit=13G
```
We'd also return 309MB. Using `_SC_PHYS_PAGES` where a value of 4118237 pages is returned then the memory value returned is substantially higher.
Diffstat (limited to 'man')
0 files changed, 0 insertions, 0 deletions