From: "Fangxiuning (Jack, EulerOS)" <fangxiuning@huawei.com>
To: jingrui <jingrui@huawei.com>, 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: Mon, 27 Jul 2020 13:40:02 +0000 [thread overview]
Message-ID: <E76E3B653DA8834F9E97D3B9694D2E5B816B7C@DGGEMI526-MBX.china.huawei.com> (raw)
In-Reply-To: <2E04DD7753BE0E4ABABF0B664610AD6F2621907D@dggeml508-mbx.china.huawei.com>
@Xiuning Would you please take a look and give some suggestion?
I don't suggest this solution for using in long term which skip call pam-systemd.so to fix this issue, Sftp sends files and call pam-systemd.so to create session which manage resources more reasonable, this is evolution direction of systemd upstream. Systemd don't have better solution and Kernel cgroup maybe give a better one for this issue.
prev parent reply other threads:[~2020-07-27 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 11:19 PROBLEM: cgroup cost too much memory when transfer small files to tmpfs 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
2020-07-24 11:35 ` Michal Hocko
2020-07-27 3:14 ` jingrui
2020-07-27 13:40 ` Fangxiuning (Jack, EulerOS) [this message]
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=E76E3B653DA8834F9E97D3B9694D2E5B816B7C@DGGEMI526-MBX.china.huawei.com \
--to=fangxiuning@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=caihaomin@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jingrui@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).