From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [blkfront] max_segments & max_segment_size Date: Fri, 15 Feb 2013 10:42:09 -0500 Message-ID: <20130215154209.GA13439@phenom.dumpdata.com> References: <1360431862.27289.8.camel@boolette.noo> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1360431862.27289.8.camel@boolette.noo> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olivier Bonvalet Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Sat, Feb 09, 2013 at 06:44:22PM +0100, Olivier Bonvalet wrote: > Hi, > > I have (very) poor write performance with Xen PV, used over RBD, and I > suppose it's because of very short values for max_segments and > max_segment_size. > (I have 250MB/s write speed in Dom0 vs 40MB/s write speed in DomU) > > >From what I read, there is already a patch to fix that, called "multi > page ring support for block devices" : > http://lists.xen.org/archives/html/xen-devel/2012-03/msg00388.html > > But it doesn't seem to have been accepted. > > So, does it exist an other solution to fix that kind of problem ? They are in development. > > Thanks, > Olivier > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >