Re: [Xen-cim] Memory pool question

[Gareth S Bestor <bestor@xxxxxxxxxx>]

I would say use CIM_Memory (a LogicalDevice) as the things to aggregate into the MemoryPool. The only situation I could see wanting to aggregate, and therefore allocate, PhysicalMemory into a pool would be for some sorta physical partitioning architecture, which Xen isnt.

Of course, that begs the next question, which is what do we do for pooling PCI slots to assign to DomUs, which Xen now supports... :-)

- Gareth

Dr. Gareth S. Bestor
IBM Linux Technology Center
M/S DES2-01
15300 SW Koll Parkway, Beaverton, OR 97006
503-578-3186, T/L 775-3186, Fax 503-578-3186

Jim Fehlig <jfehlig@xxxxxxxxxx>

Jim Fehlig <jfehlig@xxxxxxxxxx>
Sent by: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx

09/27/06 01:57 PM

To	xen-cim@xxxxxxxxxxxxxxxxxxx
cc
Subject	[Xen-cim] Memory pool question

It's not clear to me which memory object we should be using to 
'populate' a memory pool.  The System Memory Profile states that 1 
instance of CIM_Memory is used to describe the logical aspects of system 
memory and * instances of CIM_PhysicalMemory are used to describe 
physical aspects of system memory.  The two are connected via 
CIM_Realizes association.

Which of these should we use to represent the host side of memory 
resources assigned to the pool?  Perhaps more clearly stated as which 
object should we use on the 'PartComponent' property of association 
Xen_MemoryPoolComponent (CIM_ConcreteComponent)?

Jim

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim