[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0618ef7-8537-f85b-4cba-9a6fb75602f0@redhat.com>
Date: Tue, 11 Dec 2018 11:35:16 +0100
From: David Hildenbrand <david@...hat.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Oscar Salvador <osalvador@...e.de>, akpm@...ux-foundation.org,
pasha.tatashin@...een.com, dan.j.williams@...il.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] mm, memory_hotplug: Don't bail out in do_migrate_range
prematurely
On 11.12.18 11:20, Michal Hocko wrote:
> On Tue 11-12-18 10:35:53, David Hildenbrand wrote:
>> So somehow remember if we had issues with one page and instead of
>> reporting 0, report e.g. -EAGAIN?
>
> There is no consumer of the return value right now and it is not really
> clear whether we need one. I would just make do_migrate_range return void.
>
Well, this would allow optimizations like "No need to check if
everything has been migrated, I can tell you right away that it has been
done".
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists