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] xen, iscsi and resilience to short network outages

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xen, iscsi and resilience to short network outages
From: "Steve Feehan" <sfeehan@xxxxxxxxx>
Date: Mon, 13 Nov 2006 15:12:20 -0500
Delivery-date: Mon, 13 Nov 2006 12:12:45 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=S2Tn+gXhbQKp67vBveD5Jl5ymjc4vtDcXWHV+Ez+YrpWF7HnhKiW8NULgWoTq7a4A1HYDX8ZHBZ4UH5cp13mdiNc8AtbkqeIjjrVI0YRKf4o5K+9XoPb9TVZ7TzjhrW8kQBzNQuxPbviQyhOfy0zPaEjSOpOKgxrAfu9dKpUOao=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1163446026.1467.3.camel@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <2f8462f30611091141s11d4dbj80f4bf54e54d59cf@xxxxxxxxxxxxxx> <20061110085445.GA1925@xxxxxxxxx> <2f8462f30611101938p35e4d06ewc78e31445512bf38@xxxxxxxxxxxxxx> <2f8462f30611131112o5b58c1afkd549393de2731f53@xxxxxxxxxxxxxx> <1163446026.1467.3.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 11/13/06, John Madden <jmadden@xxxxxxxxxxx> wrote:
> Would I stand a better chance connecting to the iSCSI LUN from domU
> rather than from dom0? My thought is that since the dom0 is able to
> reconnect to the LUN when the network returns, perhaps this would be
> the case for domU as well?

Why would you *not* leave all of the iSCSI work to the domU?  It seems
like that would provide better predictability performance-wise (i.e.,
leaving your I/O to the built-in scheduling rather than everyone getting
a whatever's-available slice of dom0's cpu time).

Because it is not tolerant to short network outages? :)

Perhaps that is an excellent point, though I'm not familiar with IO
scheduling. But if pushing the IO up to domU makes it more reliable
then I might be able to tolerate a small loss in IO performance. This
presumes that it will be more reliable, which I won't have time to
test right away.

--
Steve Feehan

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