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-ia64-devel

Re: [Xen-ia64-devel] Xen/ia64 roadmap

To: Alex Williamson <alex.williamson@xxxxxx>
Subject: Re: [Xen-ia64-devel] Xen/ia64 roadmap
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Fri, 19 Oct 2007 11:38:05 +0900
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 18 Oct 2007 19:38:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1192738380.6388.10.camel@lappy>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1192636994.6775.30.camel@lappy> <20071018022218.GA20219%yamahata@xxxxxxxxxxxxx> <1192738380.6388.10.camel@lappy>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
On Thu, Oct 18, 2007 at 02:13:00PM -0600, Alex Williamson wrote:
> > Some random ideas. I hope they will help starting discussions.
> > 
> >         * NUMA emu (something like Linux x86_64 NUMA_EMU)
> >           This would be convenient for developing NUMA support on
> >           non-NUMA box.
> 
>    I like this idea, at least as a development feature.

As a development feature, another approach would be that enhancing
VTi domain and using nested Xen.


> >         * performance isolation
> 
>    Can you describe what you mean by this?

It was too vague.
What I'm having in mind is IO performance isolation.
Currently guest domain might be able to interfare with other domains
IO performance.
One promising approach is direct attaching hardware device to guest domain
using IOMMU or other tricks.

Another software based approach is limiting performance. 
For example, limiting disk io performance.
http://lists.xensource.com/archives/html/xen-devel/2007-07/msg00863.html
However his proposal seems to be discarded.
Is there other way? How about network?

thanks,
-- 
yamahata

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