[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190528224501.GH27847@tower.DHCP.thefacebook.com>
Date: Tue, 28 May 2019 22:45:05 +0000
From: Roman Gushchin <guro@...com>
To: "Uladzislau Rezki (Sony)" <urezki@...il.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Hillf Danton <hdanton@...a.com>,
Michal Hocko <mhocko@...e.com>,
Matthew Wilcox <willy@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Garnier <thgarnie@...gle.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@...ymobile.com>,
Steven Rostedt <rostedt@...dmis.org>,
Joel Fernandes <joelaf@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH v3 3/4] mm/vmap: get rid of one single unlink_va() when
merge
On Mon, May 27, 2019 at 11:38:41AM +0200, Uladzislau Rezki (Sony) wrote:
> It does not make sense to try to "unlink" the node that is
> definitely not linked with a list nor tree. On the first
> merge step VA just points to the previously disconnected
> busy area.
>
> On the second step, check if the node has been merged and do
> "unlink" if so, because now it points to an object that must
> be linked.
>
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@...il.com>
> Acked-by: Hillf Danton <hdanton@...a.com>
Reviewed-by: Roman Gushchin <guro@...com>
Thanks!
Powered by blists - more mailing lists