linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shakeel Butt <shakeel.butt@linux.dev>
To: "T.J. Mercier" <tjmercier@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@kernel.org>,
	 Roman Gushchin <roman.gushchin@linux.dev>,
	Muchun Song <muchun.song@linux.dev>,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org,
	Meta kernel team <kernel-team@meta.com>,
	cgroups@vger.kernel.org
Subject: Re: [PATCH 3/4] memcg: initiate deprecation of oom_control
Date: Wed, 14 Aug 2024 14:49:00 -0700	[thread overview]
Message-ID: <vhmogrjr4zehf2duzhd5treij77j6npyisch5f2vyshjztgn57@db5suilpihly> (raw)
In-Reply-To: <vixhnru2gag4wav5m2qesoihlhuce75s662ccxcekdp3ba44kj@ml7tlkaefqsx>

On Wed, Aug 14, 2024 at 02:41:13PM GMT, Shakeel Butt wrote:
> On Wed, Aug 14, 2024 at 02:00:03PM GMT, T.J. Mercier wrote:
> > On Wed, Aug 14, 2024 at 1:29 PM Shakeel Butt <shakeel.butt@linux.dev> wrote:
> > >
> > > The oom_control provides functionality to disable memcg oom-killer,
> > > notifications on oom-kill and reading the stats regarding oom-kills.
> > > This interface was mainly introduced to provide functionality for
> > > userspace oom-killers. However it is not robust enough and only supports
> > > OOM handling in the page fault path.
> > >
> > > For v2, the users can use the combination of memory.events notifications
> > > and memory.high interface to provide userspace OOM-killing functionality.
> > > Let's start the deprecation process for v1 and gather the info on how
> > > the current users are using this interface and work on providing a more
> > > robust functionality in v2.
> > >
> > > Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev>
> > > ---
> > >  Documentation/admin-guide/cgroup-v1/memory.rst | 8 ++++++--
> > >  mm/memcontrol-v1.c                             | 7 +++++++
> > >  2 files changed, 13 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/Documentation/admin-guide/cgroup-v1/memory.rst b/Documentation/admin-guide/cgroup-v1/memory.rst
> > > index afe5e95e9f7b..74cea6712d06 100644
> > > --- a/Documentation/admin-guide/cgroup-v1/memory.rst
> > > +++ b/Documentation/admin-guide/cgroup-v1/memory.rst
> > > @@ -92,6 +92,8 @@ Brief summary of control files.
> > >                                       This knob is deprecated and shouldn't be
> > >                                       used.
> > >   memory.oom_control                 set/show oom controls.
> > > +                                     This knob is deprecated and shouldn't be
> > > +                                     used.
> > >   memory.numa_stat                   show the number of memory usage per numa
> > >                                      node
> > >   memory.kmem.limit_in_bytes          Deprecated knob to set and read the kernel
> > > @@ -846,8 +848,10 @@ It's applicable for root and non-root cgroup.
> > >
> > >  .. _cgroup-v1-memory-oom-control:
> > >
> > > -10. OOM Control
> > > -===============
> > > +10. OOM Control (DEPRECATED)
> > > +============================
> > > +
> > > +THIS IS DEPRECATED!
> > >
> > >  memory.oom_control file is for OOM notification and other controls.
> > >
> > > diff --git a/mm/memcontrol-v1.c b/mm/memcontrol-v1.c
> > > index e0bb54e42011..07343e338e4e 100644
> > > --- a/mm/memcontrol-v1.c
> > > +++ b/mm/memcontrol-v1.c
> > > @@ -1907,6 +1907,9 @@ static ssize_t memcg_write_event_control(struct kernfs_open_file *of,
> > >                 event->register_event = mem_cgroup_usage_register_event;
> > >                 event->unregister_event = mem_cgroup_usage_unregister_event;
> > >         } else if (!strcmp(name, "memory.oom_control")) {
> > > +               pr_warn_once("oom_control is deprecated and will be removed. "
> > > +                            "Please report your usecase to linux-mm-@kvack.org"
> > > +                            " if you depend on this functionality. \n";
> > 
> > Missing close paren?
> 
> Ah, thanks for catching that. I compile tested the old version before
> moving text around. Anyways, will resend.
> 

Oh I was building without CONFIG_MEMCG_V1.


  reply	other threads:[~2024-08-14 21:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 20:28 [PATCH 0/4] memcg: initiate deprecation of v1 features Shakeel Butt
2024-08-14 20:28 ` [PATCH 1/4] memcg: initiate deprecation of v1 tcp accounting Shakeel Butt
2024-08-14 20:59   ` T.J. Mercier
2024-08-14 21:42     ` Shakeel Butt
2024-08-14 20:28 ` [PATCH 2/4] memcg: initiate deprecation of v1 soft limit Shakeel Butt
2024-08-14 20:28 ` [PATCH 3/4] memcg: initiate deprecation of oom_control Shakeel Butt
2024-08-14 21:00   ` T.J. Mercier
2024-08-14 21:41     ` Shakeel Butt
2024-08-14 21:49       ` Shakeel Butt [this message]
2024-08-14 21:51     ` Andrew Morton
2024-08-14 20:28 ` [PATCH 4/4] memcg: initiate deprecation of pressure_level Shakeel Butt
2024-08-14 21:01   ` T.J. Mercier

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=vhmogrjr4zehf2duzhd5treij77j6npyisch5f2vyshjztgn57@db5suilpihly \
    --to=shakeel.butt@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=tjmercier@google.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