lkml.org 
[lkml]   [2013]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH part5 0/7] Arrange hotpluggable memory as ZONE_MOVABLE.
On 08/12/2013 07:50 AM, Tejun Heo wrote:
>
> * Why can't it be opportunistic? It's silly, for example, to fail
> boot because ACPI tells the kernel that all memory is hotpluggable
> especially as there'd be plenty of memory sitting around doing
> nothing and failing to boot is one of the most grave failure mode.
> The HOTPLUG flag can be advisory, right? Try to allocate
> !hotpluggable memory first, but if that fails, ignore it and
> allocate from anywhere, much like the try_nid allocations.
>
> * Similar to the point hpa raised. If this can be made opportunistic,
> do we need the strict reordering to discover things earlier?
> Shouldn't it be possible to configure memblock to allocate close to
> the kernel image until hotplug and numa information is available?
> For most sane cases, the memory allocated will be contained in
> non-hotpluggable node anyway and in case they aren't hotplug
> wouldn't work but the system will boot and function perfectly fine.
>

It gets really messy if it is advisory. Suddenly you have the user
thinking they can hotswap a memory bank and they just can't.

Overall, I'm getting convinced that this whole approach is just doomed
to failure -- it will not provide the user what they expect and what
they need, which is to be able to hotswap any particular chunk of
memory. This means that there has to be a remapping layer, either using
the TLBs (perhaps leveraging the Xen machine page number) or using
things like QPI memory routing.

-hpa




\
 
 \ /
  Last update: 2013-08-12 17:41    [W:0.198 / U:0.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site