[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <0E1D1C04-5892-438F-9191-F23CBE1A6DC5@lca.pw>
Date: Thu, 5 Dec 2019 14:19:08 -0500
From: Qian Cai <cai@....pw>
To: Yang Shi <yang.shi@...ux.alibaba.com>
Cc: fabecassis@...dia.com, jhubbard@...dia.com, mhocko@...e.com,
cl@...ux.com, vbabka@...e.cz, mgorman@...hsingularity.net,
akpm@...ux-foundation.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [v3 PATCH] mm: move_pages: return valid node id in status if the page is already on the target node
> On Dec 5, 2019, at 1:54 PM, Yang Shi <yang.shi@...ux.alibaba.com> wrote:
>
> This is because the status is not set if the page is already on the
> target node, but move_pages() should return valid status as long as it
> succeeds. The valid status may be errno or node id.
>
> We can't simply initialize status array to zero since the pages may be
> not on node 0. Fix it by updating status with node id which the page is
> already on.
This does not look correct either.
“ENOENT
No pages were found that require moving. All pages are either already on the target node, not present, had an invalid address or could not be moved because they were mapped by multiple processes.”
move_pages() should return -ENOENT instead.
Powered by blists - more mailing lists