Skip to content

Commit b10a7f6

Browse files
mrsharmgewarren
andauthored
Update xml/System/GCMemoryInfo.xml
Co-authored-by: Genevieve Warren <[email protected]>
1 parent 0aefe85 commit b10a7f6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

xml/System/GCMemoryInfo.xml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -316,9 +316,9 @@ The memory after `OBJ_D` is not considered part of the `FragmentedBytes` but is
316316
<summary>Gets the physical memory load when the last garbage collection occurred.</summary>
317317
<value>The physical memory load, in bytes, when the last garbage collection occurred.</value>
318318
<remarks>
319-
<para>When a process is not running in a container or running in a container without a memory limit:
320-
On Windows, the MemoryLoadBytes is obtained from the <see href="/windows/win32/api/winbase/ns-winbase-memorystatus">MEMORYSTATUS structure</see> in bytes divided by the total physical memory.
321-
On Linux, the MemoryLoadBytes is obtained from reading the MemAvailable field from `/proc/meminfo` divided by the total physical memory.</para>
319+
<para>When a process is not running in a container or running in a container without a memory limit:</para>
320+
<para>- On Windows, the MemoryLoadBytes is obtained from the <see href="/windows/win32/api/winbase/ns-winbase-memorystatus">MEMORYSTATUS structure</see> in bytes divided by the total physical memory.</para>
321+
<para>- On Linux, the MemoryLoadBytes is obtained from reading the MemAvailable field from <c>/proc/meminfo</c> divided by the total physical memory.</para>
322322
<para>When a process is running in a container with a memory limit or when cgroup limits are set:
323323
On Windows, the MemoryLoadBytes is obtained from the Working Set Size field in the <see href="/windows/win32/api/psapi/nf-psapi-getprocessmemoryinfo">PROCESS_MEMORY_COUNTERS structure</see> in bytes divided by the memory limit.
324324
On Linux, the MemoryLoadBytes is obtained from the used physical memory via the CGroup Memory Usage file from `memory.usage_in_bytes` for CGroups v1 and `memory.current` for CGroups v2 divided by the memory limit. The cgroup limits don't necessarily mean there is a container. You can use cgroup to set limits on a regular process.</para>

0 commit comments

Comments
 (0)