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 backend performance

To: "Venefax" <venefax@xxxxxxxxx>, "Thomas Halinka" <lists@xxxxxxxxx>, "Stefan de Konink" <stefan@xxxxxxxxx>
Subject: RE: [Xen-users] disk backend performance
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sat, 29 Nov 2008 14:18:18 +1100
Cc: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>, Guillaume <guillaume.chardin@xxxxxxxxx>
Delivery-date: Fri, 28 Nov 2008 19:19:16 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <026501c951ce$ab14cdf0$013e69d0$@com>
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: <20081128105334.I95069-100000@xxxxxxxxxxxxx> <1227878219.25974.3.camel@ubu32> <AEC6C66638C05B468B556EA548C1A77D0154FDC6@trantor> <026501c951ce$ab14cdf0$013e69d0$@com>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclRW8Uo8ye8bC2USzaEUJFZ8pSNcwAccLXQAAA+hxAAABYA4A==
Thread-topic: [Xen-users] disk backend performance
> 
> So: over a dedicated cable with jumbo frames it is actually smarter to
use
> ISCSI than AOE? Is that your conclusion?

My conclusion was more along the lines of "don't assume that just
because iSCSI uses TCP/IP that it is inferior performance-wise to AoE".

I don't believe that there currently exist any hardware implemented AoE
adapters, but there are hardware iSCSI adapters (HBA's).

With a software implementation, Ethernet headers have to be constructed
per packet (+IP+TCP for iSCSI), error detection has to be implemented
for AoE, and packetization has to be done in software (less so for iSCSI
as most hardware has TCP Large Send Offload which from a software point
of view allows sending of 64k TCP packets). Any network adapter that
you'd use in a server these days has TX and RX checksum offloading
available, so you get checksumming of your TCP packets for free when
using software iSCSI, while for AoE you need to calculate checksums
manually in software.

With a hardware iSCSI HBA, the O/S just has to say to the card 'read x
sectors starting at y and put them in memory here'. The card does the
rest. Of course, to do this you have to buy an iSCSI HBA, which
increases the cost of the solution somewhat.

If you want to use non-disk devices then iSCSI is probably a better
choice - a robotic tape library is more likely to work over iSCSI
without problems than it will over AoE, although my information on that
sort of thing may be out of date...

A protocol called HyperSCSI exists, which is basically SCSI over
Ethernet, but I don't know how available it is.

James

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