From: jingrui <jingrui@huawei.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "tj@kernel.org" <tj@kernel.org>, Lizefan <lizefan@huawei.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"vdavydov.dev@gmail.com" <vdavydov.dev@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
caihaomin <caihaomin@huawei.com>,
"Weiwei (N)" <wick.wei@huawei.com>
Subject: 答复: PROBLEM: cgroup cost too much memory when transfer small files to tmpfs
Date: Fri, 24 Jul 2020 09:35:26 +0000 [thread overview]
Message-ID: <2E04DD7753BE0E4ABABF0B664610AD6F2620D4F6@dggeml528-mbx.china.huawei.com> (raw)
In-Reply-To: <20200724075508.GF4061@dhcp22.suse.cz>
On Friday, July 24, 2020 3:55 PM, Michal Hocko wrote:
> What is the reason to run under !root cgroup in those sessions if you do not care about accounting anyway?
The systemd not support run those sessions under root cgroup, disable
pam-systemd will not create session/cgroup, but this is not safe and make
systemd-logind not work.
> tmpfs is a persistent charge until the file is removed. So if those outlive the session then you either want them to be charged to somebody or you do not care about accounting at all, no? Or could you explain your usecase some more?
In some usecase, we dont have disk and keep files in memory, we treat tmpfs
just like disk, so dont care tmpfs accouting at all.
--
Jingrui
BR.
next prev parent reply other threads:[~2020-07-24 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 11:19 jingrui
2020-07-21 14:45 ` Shakeel Butt
2020-07-21 17:41 ` Johannes Weiner
2020-07-21 18:49 ` Roman Gushchin
2020-07-21 19:12 ` Shakeel Butt
2020-07-21 19:27 ` Roman Gushchin
2020-07-24 7:55 ` Michal Hocko
2020-07-24 9:35 ` jingrui [this message]
2020-07-24 11:35 ` 答复: " Michal Hocko
2020-07-27 3:14 ` jingrui
2020-07-27 13:40 ` 答复: " Fangxiuning (Jack, EulerOS)
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=2E04DD7753BE0E4ABABF0B664610AD6F2620D4F6@dggeml528-mbx.china.huawei.com \
--to=jingrui@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=caihaomin@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=mhocko@kernel.org \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=wick.wei@huawei.com \
/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