WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH] fix memory allocation from NUMA node for VT-d.

To: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>, Espen Skoglund <espen.skoglund@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] fix memory allocation from NUMA node for VT-d.
From: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Date: Wed, 19 Nov 2008 10:57:10 -0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: 'Keir, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Fraser' <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Wed, 19 Nov 2008 10:57:52 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20081119172029.4EF6.SHIMADA-YXB@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20081118182701.CFB8.SHIMADA-YXB@xxxxxxxxxxxxxxx> <18722.44645.241716.684143@xxxxxxxxxxxxxxxxxx> <20081119172029.4EF6.SHIMADA-YXB@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclKII5Va1zyxuq1RiSDAM/uQDS9MAAV32ZQ
Thread-topic: [Xen-devel] [PATCH] fix memory allocation from NUMA node for VT-d.
>Xen's user will assign a device to a closer guest. So, node of the
>guest and node connected to IOMMU will be the same.
>As a result, the memory performance will be improved with my patch. 

Are you assuming guest will ping the guest to a physical CPU?  How does the 
user figure out which devices are closer to which physical CPU in the platform 
in a QPI system without using proximity domain info?

Allen

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
>Yuji Shimada
>Sent: Wednesday, November 19, 2008 12:26 AM
>To: Espen Skoglund
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; 'Keir Fraser'
>Subject: Re: [Xen-devel] [PATCH] fix memory allocation from 
>NUMA node for VT-d.
>
>Hi Espen,
>
>Your suggestion allocating memory from one of the nodes where the
>IOMMU is attached improves performance more. But more memory is
>needed, because structures are needed per IOMMU.
>
>My patch keeps the current implementation, one Device Assignment
>Structure and Address Translation Structure per guest.
>
>Xen's user will assign a device to a closer guest. So, node of the
>guest and node connected to IOMMU will be the same.
>As a result, the memory performance will be improved with my patch.
>
>Thanks,
>--
>Yuji Shimada
>
>On Tue, 18 Nov 2008 12:00:37 +0000
>Espen Skoglund <espen.skoglund@xxxxxxxxxxxxx> wrote:
>
>> Given an FSB based system the IOMMUs sit in the north-bridge.  How
>> does this work qith QPI?  Where in the system do the different IOMMUs
>> sit?  Wouldn't it make more sense to allocate memory from one of the
>> nodes where the IOMMU is attached?  Having the memory allocated from
>> the node of the guest only helps when the guest needs to update its
>> page tables.  I'd rather optimize for page table walks in the IOMMU.
>> 
>>      eSk
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel