From: Yafang Shao <laoar.shao@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Dave Chinner <dchinner@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Roman Gushchin <guro@fb.com>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>, Linux MM <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] protect page cache from freeing inode
Date: Wed, 5 Feb 2020 09:19:50 +0800 [thread overview]
Message-ID: <CALOAHbChK=JNA5q-3QqyNVG34RZxmZdUOR2HvtNWHCz+EAQAaQ@mail.gmail.com> (raw)
In-Reply-To: <20200204211954.GA20584@dread.disaster.area>
On Wed, Feb 5, 2020 at 5:20 AM Dave Chinner <david@fromorbit.com> wrote:
>
> On Wed, Jan 22, 2020 at 09:46:57PM +0800, Yafang Shao wrote:
> > On Thu, Jan 9, 2020 at 12:04 AM Yafang Shao <laoar.shao@gmail.com> wrote:
> > >
> > > On my server there're some running MEMCGs protected by memory.{min, low},
> > > but I found the usage of these MEMCGs abruptly became very small, which
> > > were far less than the protect limit. It confused me and finally I
> > > found that was because of inode stealing.
> > > Once an inode is freed, all its belonging page caches will be dropped as
> > > well, no matter how may page caches it has. So if we intend to protect the
> > > page caches in a memcg, we must protect their host (the inode) first.
> > > Otherwise the memcg protection can be easily bypassed with freeing inode,
> > > especially if there're big files in this memcg.
> > > The inherent mismatch between memcg and inode is a trouble. One inode can
> > > be shared by different MEMCGs, but it is a very rare case. If an inode is
> > > shared, its belonging page caches may be charged to different MEMCGs.
> > > Currently there's no perfect solution to fix this kind of issue, but the
> > > inode majority-writer ownership switching can help it more or less.
> > >
> > > - Changes against v2:
> > > 1. Seperates memcg patches from this patchset, suggested by Roman.
> > > A separate patch is alreay ACKed by Roman, please the MEMCG
> > > maintianers help take a look at it[1].
> > > 2. Improves code around the usage of for_each_mem_cgroup(), suggested
> > > by Dave
> > > 3. Use memcg_low_reclaim passed from scan_control, instead of
> > > introducing a new member in struct mem_cgroup.
> > > 4. Some other code improvement suggested by Dave.
> > >
> > >
> > > - Changes against v1:
> > > Use the memcg passed from the shrink_control, instead of getting it from
> > > inode itself, suggested by Dave. That could make the laying better.
> > >
> > > [1]
> > > https://lore.kernel.org/linux-mm/CALOAHbBhPgh3WEuLu2B6e2vj1J8K=gGOyCKzb8tKWmDqFs-rfQ@mail.gmail.com/
> > >
> > > Yafang Shao (3):
> > > mm, list_lru: make memcg visible to lru walker isolation function
> > > mm, shrinker: make memcg low reclaim visible to lru walker isolation
> > > function
> > > memcg, inode: protect page cache from freeing inode
> > >
> > > fs/inode.c | 78 ++++++++++++++++++++++++++++++++++++++++++++--
> > > include/linux/memcontrol.h | 21 +++++++++++++
> > > include/linux/shrinker.h | 3 ++
> > > mm/list_lru.c | 47 +++++++++++++++++-----------
> > > mm/memcontrol.c | 15 ---------
> > > mm/vmscan.c | 27 +++++++++-------
> > > 6 files changed, 143 insertions(+), 48 deletions(-)
> > >
> >
> > Dave, Johannes,
> >
> > Any comments on this new version ?
>
> Sorry, I lost track of this amongst travel and conferences mid
> january. Can you update and post it again once -rc1 is out?
>
Sure, I will do it.
Thanks for your reply.
Thanks
Yafang
prev parent reply other threads:[~2020-02-05 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 16:03 Yafang Shao
2020-01-08 16:03 ` [PATCH v3 1/3] mm, list_lru: make memcg visible to lru walker isolation function Yafang Shao
2020-01-08 16:03 ` [PATCH v3 2/3] mm, shrinker: make memcg low reclaim " Yafang Shao
2020-01-08 16:03 ` [PATCH v3 3/3] memcg, inode: protect page cache from freeing inode Yafang Shao
2020-01-22 13:46 ` [PATCH v3 0/3] " Yafang Shao
2020-02-04 21:19 ` Dave Chinner
2020-02-05 1:19 ` Yafang Shao [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='CALOAHbChK=JNA5q-3QqyNVG34RZxmZdUOR2HvtNWHCz+EAQAaQ@mail.gmail.com' \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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