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/13/2013 12:46 AM, Tejun Heo wrote:
> Hello, Tang.
......
>
>> But, different users have different ways to use memory hotplug.
>>
>> Hotswaping any particular chunk of memory is the goal we will reach
>> finally. But it is on specific hardware. In most current machines, we
>> can use movable node to manage resource in node unit.
>>
>> And also, without this movablenode boot option, the MOVABLE_NODE
>> functionality, which is already in the kernel, will not be able to
>> work. All nodes has kernel memory means no movable node.
>>
>> So, how about this: Just like MOVABLE_NODE functionality, introduce
>> a new config option. When we have better solutions for memory hotplug,
>> we shutoff or remove the config and related code.
>>
>> For now, at least make movable node work.

Hi tj,
cc hpa,

I explained above because hpa said he thought the whole approach is
wrong. I think node hotplug is meaningful for users. And without this
patch-set, MOVABLE_NODE means nothing. This is all above.

Since you replied his email in previous emails, I just replied to
answer both of you. Sorry for the misunderstanding. :)

>
> We are talking completely past each other. I'll just try to clarify
> what I was saying. Can you please do the same? Let's re-sync on the
> discussion.
>
> * Adding an option to tell the kernel to try to stay away from
> hotpluggable nodes is fine. I have no problem with that at all.

Agreed.

>
> * The patchsets upto this point have been somehow trying to reorder
> operations shomehow such that *no* memory allocation happens before
> memblock is populated with hotplug information.

Yes, this is exactly what I want to do.

>
> * However, we already *know* that the memory the kernel image is
> occupying won't be removeable. It's highly likely that the amount
> of memory allocation before NUMA / hotplug information is fully
> populated is pretty small. Also, it's highly likely that small
> amount of memory right after the kernel image is contained in the
> same NUMA node, so if we allocate memory close to the kernel image,
> it's likely that we don't contaminate hotpluggable node. We're
> talking about few megs at most right after the kernel image. I
> can't see how that would make any noticeable difference.

This point, I don't quite agree. What you said is highly likely, but
not definitely. Users may find they lost hotpluggable memory.

The node the kernel resides in won't be removable. This is agreed.
But I still want SRAT earlier for the following reasons:

1. For a production provided to users, the firmware specified how
many nodes are hotpluggable. When the system is up, if users
found they lost movable nodes, I think it could be messy.

2. Reorder SRAT parsing earlier is not that difficult to do. The
only procedures reordered are acpi tables initialization and
acpi_initrd_override. The acpi part patches are being reviewed.
And it is better solution. If possible, I think we should do it.

In summary, I don't want early memory allocation with hotpluggable
memory to be opportunistic.

>
> * Once hotplug information is available, allocation can happen as
> usual and the kernel can report the nodes which are actually
> hotpluggable - marked as hotpluggable by the firmware&& didn't get
> contaminated during early alloc&& didn't get overflow allocations
> afterwards. Note that we need such mechanism no matter what as the
> kernel image can be loaded into hotpluggable nodes and reporting
> that to userland is the only thing the kernel can do for cases like
> that short of denying memory unplug on such nodes.

Agreed.

>
> The whole thing would be a lot simpler and generic. It doesn't even
> have to care about which mechanism is being used to acquire all those
> information. What am I missing here?

Sorry for the misunderstanding.

Thanks. :)



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