public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tracy Reed <treed@ultraviolet.org>
To: pasik@iki.fi, xen-devel@lists.xensource.com,
	Aoetools-discuss@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] domU is causing misaligned disk writes
Date: Tue, 20 Apr 2010 14:58:59 -0700	[thread overview]
Message-ID: <20100420215859.GW5660@tracyreed.org> (raw)
In-Reply-To: <20100420204151.GH1708@kremvax.cs.ubc.ca>

[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]

On Tue, Apr 20, 2010 at 01:41:51PM -0700, Brendan Cully spake thusly:
> You could also be limited by the size of the block request ring (I
> believe the ring is normally only one page) -- the ring needs to be
> large enough to handle the bandwidth delay product, and AoE means the
> delay is probably higher than normal.

Interesting. Any easy way to increase this as a test?

> Do you get better performance against a local partition?

You mean a local partition on local disk in the dom0 given to a domU
as xvd? Let's see...

I just created a 20G logical volume on the dom0:

# /usr/sbin/lvcreate -n test -L20G sysvg

Added it to the domain config file to be /dev/xvdi and rebooted.

         "phy:/dev/sysvg/test,xvdi,w"

I know you can attach block devices on the fly but this has not been
entirely reliable for me in the past so I reboot now.

In domU against xvdi which is /dev/sysvg/test in dom0:

# dd if=/dev/zero of=/dev/xvdi bs=4096 count=1000000
1000000+0 records in
1000000+0 records out
4096000000 bytes (4.1 GB) copied, 99.3749 seconds, 41.2 MB/s

And iostat on dom0 shows:
Device:         rrqm/s   wrqm/s   r/s   w/s    rkB/s    wkB/s avgrq-sz
avgqu-sz   await  svctm  %util
sda               0.00   824.00  4.00 101.00    16.00 39936.00
760.99     3.19   31.31   9.52 100.00

In dom0 against the local disk to demonstrate native performance:

# dd if=/dev/zero of=/dev/sysvg/test bs=4096 count=1000000
1000000+0 records in
1000000+0 records out
4096000000 bytes (4.1 GB) copied, 84.9047 seconds, 48.2 MB/s

Device:         rrqm/s   wrqm/s   r/s   w/s    rkB/s    wkB/s avgrq-sz
avgqu-sz   await  svctm  %util
sda               7.00 11104.00  5.00 96.00    48.00 48144.00   954.30
133.92 1172.40   9.94 100.40

Virtually no reads happening. This disk seems a bit slow (older 80G
sata disk) but otherwise normal. I don't see anything indicating
alignment issues.

-- 
Tracy Reed
http://tracyreed.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2010-04-20 21:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20  8:09 domU is causing misaligned disk writes Tracy Reed
2010-04-20  8:49 ` [Xen-devel] " Pasi Kärkkäinen
2010-04-20  8:54   ` Pasi Kärkkäinen
     [not found]     ` <20100420184038.GB32720@phenom.dumpdata.com>
2010-04-20 22:58       ` [LKML] " Tracy Reed
2010-04-20 19:39   ` Tracy Reed
2010-04-20 19:54     ` Pasi Kärkkäinen
2010-04-20 20:03       ` Tracy Reed
2010-04-20 20:00   ` Tracy Reed
2010-04-20 20:25     ` Konrad Rzeszutek Wilk
2010-04-20 21:19       ` Tracy Reed
2010-04-28 19:55         ` [Aoetools-discuss] " Gabor Gombas
2010-04-20 20:41     ` Brendan Cully
2010-04-20 21:58       ` Tracy Reed [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=20100420215859.GW5660@tracyreed.org \
    --to=treed@ultraviolet.org \
    --cc=Aoetools-discuss@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xensource.com \
    /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