linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: =?gb18030?B?xP6+srXEzOy/1Q==?= <497692757@qq.com>
To: =?gb18030?B?dGo=?= <tj@kernel.org>,
	=?gb18030?B?bGl6ZWZhbg==?= <lizefan@huawei.com>,
	=?gb18030?B?aGFubmVz?= <hannes@cmpxchg.org>
Cc: =?gb18030?B?bGludXgtbW0=?= <linux-mm@kvack.org>
Subject: Can Cgroup memory subsystem provide estimated available memory, just like /proc/meminfo: MemAvailable?
Date: Fri, 7 Oct 2022 23:58:04 +0800	[thread overview]
Message-ID: <tencent_079841A2079F41280FA265E5404743AD7008@qq.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 608 bytes --]

Hello cgroup experts,


/proc/meminfo: MemAvailable is a very useful mertics,&nbsp;provide estimated available memory, caculated by MemFree, Active(file), Inactive(file), SReclaimable and watermarks. It is implemented by the si_mem_available() function[1]. Can cgroup memory subsystem provide estimated available memory?


/proc/meminfo:
MemTotal:&nbsp; &nbsp; &nbsp; &nbsp;63793888 kB
MemFree:&nbsp; &nbsp; &nbsp; &nbsp; 21124704 kB
MemAvailable:&nbsp; &nbsp;39106088 kB


[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34e431b0ae398fc54ea69ff85ec700722c9da773

[-- Attachment #2: Type: text/html, Size: 812 bytes --]

             reply	other threads:[~2022-10-07 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 15:58 =?gb18030?B?xP6+srXEzOy/1Q==?= [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-08  9:09 Can Cgroup memory subsystem provide estimated available memory, just like /proc/meminfo: MemAvailable? =?gb18030?B?xP6+srXEzOy/1Q==?=
2022-10-08  9:29 Can cgroup " 王欢(云痕)
2022-10-08  9:45 王欢(云痕)
2022-10-08  9:48 王欢(云痕)
2022-10-08 10:38 王欢(云痕)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tencent_079841A2079F41280FA265E5404743AD7008@qq.com \
    --to=497692757@qq.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=lizefan@huawei.com \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).