From: Yafang Shao <laoar.shao@gmail.com>
To: Michal Hocko <mhocko@suse.com>
Cc: hannes@cmpxchg.org, roman.gushchin@linux.dev,
shakeel.butt@linux.dev, muchun.song@linux.dev,
akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/2] memcg: add nomlock to avoid folios beling mlocked in a memcg
Date: Mon, 6 Jan 2025 22:04:31 +0800 [thread overview]
Message-ID: <CALOAHbA+_jPqqMvzppwu1ffmQwA7ZofzrnhTewKK4C_3Dwoj6Q@mail.gmail.com> (raw)
In-Reply-To: <Z3vM_lLbzlAJvdSX@tiehlicka>
On Mon, Jan 6, 2025 at 8:30 PM Michal Hocko <mhocko@suse.com> wrote:
>
> On Wed 25-12-24 10:23:53, Yafang Shao wrote:
> [...]
> > - Option C: Reparent the mlocked page to a common ancestor
> >
> > Consider the following hierarchical:
> >
> > A
> > / \
> > B C
> >
> > If B is mlocking a page in C, we can reparent that mlocked page to A,
> > essentially making A the new parent for the mlocked page.
>
> How does this solve the underlying problem?
No OOM will occur in C until the limit of A is reached, and an OOM at
that point is the expected behavior.
In simpler terms: move the shared resource to a shared layer. I
believe this will resolve most of the issues caused by the shared
resources.
--
Regards
Yafang
next prev parent reply other threads:[~2025-01-06 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 7:34 Yafang Shao
2024-12-15 7:34 ` [RFC PATCH 1/2] mm/memcontrol: add a new cgroup file memory.nomlock Yafang Shao
2024-12-15 7:34 ` [RFC PATCH 2/2] mm: Add support for nomlock to avoid folios beling mlocked in a memcg Yafang Shao
2024-12-20 10:23 ` [RFC PATCH 0/2] memcg: add " Michal Hocko
2024-12-20 11:52 ` Yafang Shao
2024-12-21 7:21 ` Michal Hocko
2024-12-22 2:34 ` Yafang Shao
2024-12-25 2:23 ` Yafang Shao
2025-01-06 12:30 ` Michal Hocko
2025-01-06 14:04 ` Yafang Shao [this message]
2025-01-07 8:39 ` Michal Hocko
2025-01-07 9:43 ` Yafang Shao
2025-01-06 12:28 ` Michal Hocko
2025-01-06 13:59 ` Yafang Shao
2025-01-07 10:04 ` Michal Hocko
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=CALOAHbA+_jPqqMvzppwu1ffmQwA7ZofzrnhTewKK4C_3Dwoj6Q@mail.gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
/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