From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Chris Down <chris@chrisdown.name>
Cc: Michal Hocko <mhocko@kernel.org>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: Memory CG and 5.1 to 5.6 uprade slows backup
Date: Thu, 9 Apr 2020 17:40:42 +0200 [thread overview]
Message-ID: <20200409174042.2a3389ba@hemera.lan.sysophe.eu> (raw)
In-Reply-To: <20200409152417.GB1040020@chrisdown.name>
On Thu, 9 Apr 2020 16:24:17 +0100 wrote:
> Bruno Prémont writes:
> >Could it be that cache is being prevented from being reclaimed by a task
> >in another cgroup?
> >
> >e.g.
> > cgroup/system/backup
> > first reads $files (reads each once)
> > cgroup/workload/bla
> > second&more reads $files
> >
> >Would $files remain associated to cgroup/system/backup and not
> >reclaimed there instead of being reassigned to cgroup/workload/bla?
>
> Yes, that's entirely possible. The first cgroup to fault in the pages is
> charged for the memory. Other cgroups may use them, but they are not accounted
> for as part of that other cgroup. They may also still be "active" as a result
> of use by another cgroup.
But the memory would then be 'active' in the original cgroup? which is
not the case here I feel.
If the remain inactive-unreclaimable in the first cgroup due to use in
another cgroup that would be at least surprising.
Doubling the high value helped (but for how long?), back with
memory.current around memory.high nut no throttling yet. But from
increase until now memory.pressure is small/zero.
Capturing
memory.stat:pgscan 47519855
memory.stat:pgsteal 44933838
over time for Michal and will report back later this evening.
When seen stuck backup was reading a multi-GiB file with
open(, O_NOATIME)
while (read()) {
transform and write to network
}
close()
thus plain sequential file read through file cache (and for this
backup run, only files not in use by anyone else, or some being
just appended to by others).
Bruno
next prev parent reply other threads:[~2020-04-09 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 9:25 Memory CG and 5.1 to 5.6 uprade slows backup Bruno Prémont
2020-04-09 9:46 ` Michal Hocko
2020-04-09 10:17 ` Bruno Prémont
2020-04-09 10:34 ` Michal Hocko
2020-04-09 15:09 ` Bruno Prémont
2020-04-09 15:24 ` Chris Down
2020-04-09 15:40 ` Bruno Prémont [this message]
2020-04-09 17:50 ` Chris Down
2020-04-09 17:56 ` Chris Down
2020-04-09 15:25 ` Michal Hocko
2020-04-10 7:15 ` Bruno Prémont
2020-04-10 8:43 ` Bruno Prémont
[not found] ` <20200410115010.1d9f6a3f@hemera.lan.sysophe.eu>
[not found] ` <20200414163134.GQ4629@dhcp22.suse.cz>
2020-04-15 10:17 ` Bruno Prémont
2020-04-15 10:24 ` Michal Hocko
2020-04-15 11:37 ` Bruno Prémont
2020-04-14 15:09 ` Bruno Prémont
2020-04-09 10:50 ` Chris Down
2020-04-09 11:58 ` Bruno Prémont
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=20200409174042.2a3389ba@hemera.lan.sysophe.eu \
--to=bonbons@linux-vserver.org \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.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).