Re: [PATCH] mm, memory_hotplug: Don't bail out in do_migrate_range prematurely

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: David Hildenbrand <david@xxxxxxxxxx>
Subject: Re: [PATCH] mm, memory_hotplug: Don't bail out in do_migrate_range prematurely
From: Michal Hocko <mhocko@xxxxxxxxxx>
Date: Tue, 11 Dec 2018 11:20:14 +0100
Cc: Oscar Salvador <osalvador@xxxxxxx>, akpm@xxxxxxxxxxxxxxxxxxxx, pasha.tatashin@xxxxxxxxxx, dan.j.williams@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
In-reply-to: <5e3e33e3-bea8-249c-2b05-665f40d70df4@redhat.com>
References: <20181211085042.2696-1-osalvador@suse.de> <5e3e33e3-bea8-249c-2b05-665f40d70df4@redhat.com>
User-agent: Mutt/1.10.1 (2018-07-13)

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.
-- 
Michal Hocko
SUSE Labs

Follow-Ups:
- Re: [PATCH] mm, memory_hotplug: Don't bail out in do_migrate_range prematurely
  - From: David Hildenbrand

References:
- [PATCH] mm, memory_hotplug: Don't bail out in do_migrate_range prematurely
  - From: Oscar Salvador
- Re: [PATCH] mm, memory_hotplug: Don't bail out in do_migrate_range prematurely
  - From: David Hildenbrand

Prev by Date: Re: [PATCH] mm, sparse: remove check with __highest_present_section_nr in for_each_present_section_nr()
Next by Date: Re: [PATCH] mm, sparse: remove check with __highest_present_section_nr in for_each_present_section_nr()
Previous by thread: Re: [PATCH] mm, memory_hotplug: Don't bail out in do_migrate_range prematurely
Next by thread: Re: [PATCH] mm, memory_hotplug: Don't bail out in do_migrate_range prematurely
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]