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-users

Re: [Xen-users] disk access besk practice

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] disk access besk practice
From: John Madden <jmadden@xxxxxxxxxxx>
Date: Tue, 6 Jan 2009 13:56:04 -0500
Delivery-date: Tue, 06 Jan 2009 10:58:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <6BDB134C-4C25-4474-BDEA-4F5FEE7101E2@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <6BDB134C-4C25-4474-BDEA-4F5FEE7101E2@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6 (enterprise 0.20070907.709405)
> While performance seems fine both interactively and using benchmarks,
> is there a practical limit to the image size before I should start
> breaking it up?

I do *everything* through physical allocations -- phy: -- and I'm quite happy 
with it.  tap:aio seems like unnecessary overhead.

John




-- 
John Madden
Sr. UNIX Systems Engineer
Ivy Tech Community College of Indiana
jmadden@xxxxxxxxxxx

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

<Prev in Thread] Current Thread [Next in Thread>