[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALvZod4nG-6DBy_sJKbCg+xrYf1DS2ZJ3zkbHQSc4q8iZiPjwQ@mail.gmail.com>
Date: Wed, 18 Nov 2020 12:07:40 -0800
From: Shakeel Butt <shakeelb@...gle.com>
To: Michal Hocko <mhocko@...e.com>
Cc: Roman Gushchin <guro@...com>, Johannes Weiner <hannes@...xchg.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] memcg, kmem: further deprecate kmem.limit_in_bytes
On Wed, Nov 18, 2020 at 11:58 AM Michal Hocko <mhocko@...e.com> wrote:
>
> On Wed 18-11-20 09:57:26, Shakeel Butt wrote:
> > The deprecation process of kmem.limit_in_bytes started with the commit
> > 0158115f702 ("memcg, kmem: deprecate kmem.limit_in_bytes") which also
> > explains in detail the motivation behind the deprecation. To summarize,
> > it is the unexpected behavior on hitting the kmem limit. This patch
> > moves the deprecation process to the next stage by disallowing to set
> > the kmem limit. In future we might just remove the kmem.limit_in_bytes
> > file completely.
> >
> > Signed-off-by: Shakeel Butt <shakeelb@...gle.com>
>
> I am not against this. I am just not sure whether one year is enough for
> those users who tend to have a more considervative kernel upgrade path.
> I am not worried about SLES user base much as we didn't even enable
> KMEM accounting when it was still guarded by a config option. Not sure
> about others though.
>
> Considering the code cleanup is not that large,
I was thinking of removing the kmem page counter in the followup but
thought of sending this alone to see if now is the right time.
> I would rather wait some
> more. But you can add
> Acked-by: Michal Hocko <mhocko@...e.com>
>
> Maybe we can ask Andrew to put it into mmotm for few releases.
>
Ok with me. I will send the full series and will ask Andrew to keep
the series in mm tree for a couple of releases.
Powered by blists - more mailing lists