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] blkif shared ring

To: "Samvel Yuri" <samvelox@xxxxxxxxx>
Subject: Re: [Xen-devel] blkif shared ring
From: "Geoffrey Lefebvre" <geoffrey@xxxxxxxxx>
Date: Tue, 18 Nov 2008 17:16:21 -0800
Cc: Dutch Meyer <dmeyer@xxxxxxxxx>, Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Andrew Warfield <andy@xxxxxxxxx>
Delivery-date: Tue, 18 Nov 2008 17:16:51 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=SLSCCFcVMd5WBvf9mw1Q7Z5z1I5E8/1dnGkVPVVkyGg=; b=GXVu3km4CknfD7dNpjoQnLBS+rsJ0oEuPaCVrJIwM28/+K/ozN1sIE9NYcRFiWhjEL r9qvc7PUIeeQycgXP++DSMAa0sZ8C5qoDgbnoHqLwLHUcDqx/73kpsLnTCrnj1S0PmOW jeIb2NcrXrv/seMNlWGp7se2SSgXb/35Ziy/o=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=NxYqf/IreYRlUoRVOhYduYtqTHfWU90IYVRtUwCJNiGZ/M6vCmIHOun/DDBmdE6P6x uZw0AwHVBPT/oMhScYB7YAR4FFPd6WubScqhNMYofFpVea0Vm2j/qXwGN2GrkxP2FMxg hSYzqcoNmCm1RNeGZj8RDIYCjxqXxyo57C2UQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <311346.33122.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <663860.81684.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20081118233943.GG5060@xxxxxxxxxxxxxxxxxxxxxxxxx> <311346.33122.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Nov 18, 2008 at 3:49 PM, Samvel Yuri <samvelox@xxxxxxxxx> wrote:
>
> hi Samuel-
>
> Would you please explain what do you mean by "using the whole buffer page"?
>
> Parallax (project of University of British Columbia) modified XEN by
> allocating an
> additional shared ring page in the blkback driver. Probably one of options?
>

Hi,

Regarding Parallax, we added support for multi-page ring to increase
the throughput of a guest block device when using an iscsi filer as a
backend. The single page ring is enough to saturate a standard SATA
drive but we got a noticeable performance increase (from 65 to a
105MBps I think) when we doubled the ring size with the iscsi backend.

I remember seeing multi-page ring patches for mini-os and fs-back from
Samuel. Is there a plan to generalize these patches to
blkfront/back/tap?

We had patches for blkfront, blkback and blktap. The size of the ring
was a compile time option for blkfront. The patches are pretty old
(3.1 I think) but could probably be refreshed without too much effort.

geoffrey

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

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