Re: [PATCH] Remove memblks from the kernel

[Yasunori Goto]

Hello. 

> This patch removes memblks from the kernel ... we don't use them, and
> the NUMA API that was planning to use them when they were originally 
> designed isn't going to use them anymore. They're just unnecessary 
> added complexity now ... time for them to go.
> 
> There's a slight complication in that ia64 uses something with a similar
> name for part of its memory layout, but Jes Sorensen kindly untangled them
> from each other for us. The patch with his modifications is below. Jes 
> tested it on ia64, and I testbuilt it with every config in my arsenal.
> 
> Please apply ... thanks,

I suppose that memblk isn't meaningless from memory hotplug standpoint.
If 1 node includes some memblks, I might be able to make partial
memory offline on the node.

For example, there are a machine which has 2 node like this figure.

   node 0             node 1
   +--------+        +--------+
   |        |        |        |
   |--------|        |--------|
   |        |--------|memblk X|
   |--------|        |--------|
   |        |        |        |
   +--------+        +--------+
  
If memory failure (like 1xECC error) occur on node 1, 
what unit should be removed? 
If only node structure, memory hotplug system has to 
remove whole memory of node 1.
But user sometimes needs much time to prepare new node for exchange.
(Becouse cost is expensive, the system is non-stop-system, etc....)

If there are some memblks in the node like figure,
the system can remove only memblk X.
So, the server can work nearer condition before failure,
and user can keep their software performance till preparing new node.

I don't have any patch of this yet, because memory hotplug need 
much other work.


But....How do you think this idea?

Thanks.

-- 
Yasunori Goto <ygoto at fsw.fujitsu.com>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/