xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Steven Haigh <netwiz@crc.id.au>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: 4.2.1: Poor write performance for DomU.
Date: Fri, 8 Mar 2013 10:54:38 +0100	[thread overview]
Message-ID: <5139B55E.3030703@citrix.com> (raw)
In-Reply-To: <5139B35A.9020406@crc.id.au>

On 08/03/13 10:46, Steven Haigh wrote:
> On 8/03/2013 8:43 PM, Roger Pau Monné wrote:
>> On 08/03/13 09:54, Steven Haigh wrote:
>>> Just wondering if there is any further news or tests that I might be
>>> able to do on this?
>>
>> I have been working on speed improvements for blkfront/blkback, and
>> submitted the first RFC series of patches last week, which can be found
>> at http://thread.gmane.org/gmane.linux.kernel/1448584. This is still a
>> WIP, so if you want to test them please be aware there might be hidden
>> bugs. I've also pushed them to a branch in my git repo:
>>
>> git://xenbits.xen.org/people/royger/linux.git xen-block-indirect
>>
>> You will need to recompile both the Dom0/DomU kernels (if they are not
>> the same) if you want to test them.
>>
> 
> Hmm - how will this react with using say, a stock kernel in the DomU (ie
> EL6.3 kernel) but these changes in the Dom0?

It should work, but you won't be able to see much performance
improvements (if any at all). Anyway, I've just referred to this series
for testing, but this should not be used on anything that's supposed to
be stable/production.

  reply	other threads:[~2013-03-08  9:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20  2:10 4.2.1: Poor write performance for DomU Steven Haigh
2013-02-20  8:26 ` Roger Pau Monné
2013-02-20  8:49   ` Steven Haigh
2013-02-20  9:49     ` Steven Haigh
2013-02-20 10:12       ` Jan Beulich
2013-02-20 11:06         ` Andrew Cooper
2013-02-20 11:08           ` Steven Haigh
2013-02-20 12:48             ` Andrew Cooper
2013-02-20 13:18             ` Pasi Kärkkäinen
2013-03-08 20:42               ` Konrad Rzeszutek Wilk
2013-03-08  8:54       ` Steven Haigh
2013-03-08  9:43         ` Roger Pau Monné
2013-03-08  9:46           ` Steven Haigh
2013-03-08  9:54             ` Roger Pau Monné [this message]
2013-03-08 20:49         ` Konrad Rzeszutek Wilk
2013-03-08 22:30           ` Steven Haigh
2013-03-11 13:30             ` Konrad Rzeszutek Wilk
2013-03-11 13:37               ` Steven Haigh
2013-03-12 13:04                 ` Konrad Rzeszutek Wilk
2013-03-12 14:08                   ` Steven Haigh
     [not found]                   ` <514EA337.7030303@crc.id.au>
     [not found]                     ` <514EA6B0.8010504@crc.id.au>
     [not found]                       ` <514EA741.7050403@crc.id.au>
2013-03-24  9:10                         ` Steven Haigh
2013-03-24  9:54                           ` Steven Haigh
2013-03-25  2:21                           ` Steven Haigh
2013-08-20 16:48                             ` Konrad Rzeszutek Wilk
2013-08-20 18:25                               ` Steven Haigh
2013-09-05  8:28                               ` Steven Haigh
2013-09-06 13:33                                 ` Konrad Rzeszutek Wilk
2013-09-06 23:06                                   ` Steven Haigh
2013-09-06 23:37                                     ` Konrad Rzeszutek Wilk

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=5139B55E.3030703@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=netwiz@crc.id.au \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).