[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221219144252.f3da256e75e176905346b4d1@linux-foundation.org>
Date: Mon, 19 Dec 2022 14:42:52 -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 Sat, 17 Dec 2022 10:57:06 +0100 Michal Hocko <mhocko@...e.com> wrote:
> > 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.
>
> Sure if we can converge to a proper implementation during the rc phase
> then it would be ok. I cannot speak for others but at least for me
> upcoming 2 weeks would be mostly offline so I cannot really contribute
> much. A revert would be much more easier from the coordination POV IMHO.
>
> Also I do not think there is any strong reason to rush this in. I do not
> really see any major problems to have this extension in 6.2
I'll queue the revert in mm-unstable with a plan to merge it upstream
around the -rc5 timeframe if there hasn't been resolution.
Please check Mina's issues with this revert's current changelog and
perhaps send along a revised one.
Powered by blists - more mailing lists