[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9731e7ff-6c0c-419f-5237-decf9a54e8f3@linux.alibaba.com>
Date: Thu, 5 Dec 2019 13:59:44 -0800
From: Yang Shi <yang.shi@...ux.alibaba.com>
To: Christopher Lameter <cl@...ux.com>
Cc: fabecassis@...dia.com, jhubbard@...dia.com, mhocko@...e.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 12/5/19 11:45 AM, Christopher Lameter wrote:
> On Fri, 6 Dec 2019, Yang Shi wrote:
>
>> Felix Abecassis reports move_pages() would return random status if the
>> pages are already on the target node by the below test program:
> Looks ok.
>
> Acked-by: Christoph Lameter <cl@...ux.com>
>
> Nitpicks:
>
>> @@ -1553,7 +1555,7 @@ static int add_page_for_migration(struct mm_struct *mm, unsigned long addr,
>> if (PageHuge(page)) {
>> if (PageHead(page)) {
>> isolate_huge_page(page, pagelist);
>> - err = 0;
>> + err = 1;
> Add a meaningful constant instead of 1?
Since it just returns errno, 0 and 1 it sounds not worth a constant or enum.
>
>> out:
>> up_read(&mm->mmap_sem);
>> +
>> return err;
> Dont do that.
Yes, my fat finger.
Powered by blists - more mailing lists