From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Olivier Bonvalet <xen.list@daevel.fr>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [blkfront] max_segments & max_segment_size
Date: Fri, 15 Feb 2013 10:42:09 -0500 [thread overview]
Message-ID: <20130215154209.GA13439@phenom.dumpdata.com> (raw)
In-Reply-To: <1360431862.27289.8.camel@boolette.noo>
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
>
prev parent reply other threads:[~2013-02-15 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 17:44 [blkfront] max_segments & max_segment_size Olivier Bonvalet
2013-02-15 15:42 ` Konrad Rzeszutek Wilk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130215154209.GA13439@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
--cc=xen.list@daevel.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.