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>,
"Fangxiuning (Jack, EulerOS)" <fangxiuning@huawei.com>
Subject: RE: 答复: PROBLEM: cgroup cost too much memory when transfer small files to tmpfs
Date: Mon, 27 Jul 2020 03:14:28 +0000 [thread overview]
Message-ID: <2E04DD7753BE0E4ABABF0B664610AD6F2621907D@dggeml508-mbx.china.huawei.com> (raw)
In-Reply-To: <20200724113530.GH4061@dhcp22.suse.cz>
Cc Fangxiuning
On Fri 24-07-20 09:35:26, jingrui wrote:
>
> 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.
Could you be more specific please?
As I know, when user call sftp client to send files, the server will call pam-systemd.so lib to create session and cgroup.
We can skip call pam-systemd.so by config /etc/pam.d/password-auth drop the line " -session optional pam_systemd.so".
But this config is global, and will affect other services, such as ssh login. We don’t find a way just don’t create cgroup dir for sftp.
@Xiuning Would you please take a look and give some suggestion?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-07-27 3:14 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
2020-07-24 11:35 ` Michal Hocko
2020-07-27 3:14 ` jingrui [this message]
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=2E04DD7753BE0E4ABABF0B664610AD6F2621907D@dggeml508-mbx.china.huawei.com \
--to=jingrui@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=caihaomin@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=fangxiuning@huawei.com \
--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