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

Re: [Xen-devel] Problems with merlot* AMD Opteron 6376 systems (Was Re: stable trees (was: [xen-4.2-testing test] 58584: regressions))



>>> On 24.06.15 at 14:29, <dario.faggioli@xxxxxxxxxx> wrote:
> On Wed, 2015-06-24 at 10:38 +0100, Ian Campbell wrote:
>> The memory info
>> Jun 23 15:56:27.749008 (XEN) Memory location of each domain:
>> Jun 23 15:56:27.756965 (XEN) Domain 0 (total: 131072):
>> Jun 23 15:56:27.756983 (XEN)     Node 0: 126905
>> Jun 23 15:56:27.756998 (XEN)     Node 1: 0
>> Jun 23 15:56:27.764952 (XEN)     Node 2: 4167
>> Jun 23 15:56:27.764969 (XEN)     Node 3: 0
>> suggests at least a small amount of cross-node memory allocation (16M
>> out of dom0s 512M total). That's probably small enough to be OK.
>> 
> Yeah, that is in line with what you usually get with dom0_nodes. Most of
> the memory, as you noted, comes from the proper node. We're just not
> (yet?) at the point where _all_ of it can come from there.

Actually as long as there is enough memory on the requested node
(minus any amount set aside for the DMA pool), this shouldn't
happen (and I had seen this to be clean in my own testing). There
being 8Gb per node, I see no immediate reason why memory from
node 2 would be handed out. Still I wouldn't suspect this to matter
here.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.