[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221216101820.3f4a370af2c93d3c2e78ed8a@linux-foundation.org>
Date: Fri, 16 Dec 2022 10:18:20 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Michal Hocko <mhocko@...e.com>
Cc: Mina Almasry <almasrymina@...gle.com>, Tejun Heo <tj@...nel.org>,
Zefan Li <lizefan.x@...edance.com>,
Johannes Weiner <hannes@...xchg.org>,
Jonathan Corbet <corbet@....net>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Shakeel Butt <shakeelb@...gle.com>,
Muchun Song <songmuchun@...edance.com>,
Huang Ying <ying.huang@...el.com>,
Yang Shi <yang.shi@...ux.alibaba.com>,
Yosry Ahmed <yosryahmed@...gle.com>, weixugc@...gle.com,
fvdl@...gle.com, bagasdotme@...il.com, cgroups@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH] Revert "mm: add nodes= arg to memory.reclaim"
On Fri, 16 Dec 2022 10:54:16 +0100 Michal Hocko <mhocko@...e.com> wrote:
> I have noticed that the patch made it into Linus tree already. Can we
> please revert it because the semantic is not really clear and we should
> really not create yet another user API maintenance problem.
Well dang. I was waiting for the discussion to converge, blissfully
unaware that the thing was sitting in mm-stable :( I guess the
Acked-by: Michal Hocko <mhocko@...e.com>
Acked-by: Shakeel Butt <shakeelb@...gle.com>
Acked-by: Muchun Song <songmuchun@...edance.com>
fooled me.
I think it's a bit premature to revert at this stage. Possibly we can
get to the desired end state by modifying the existing code. Possibly
we can get to the desired end state by reverting this and by adding
something new.
If we can't get to the desired end state at all then yes, I'll send
Linus a revert of this patch later in this -rc cycle.
Powered by blists - more mailing lists