All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Duy Le (Dan)" <duyle.vn@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Host's write request is 4KB larger than that of the guest?
Date: Thu, 06 Jan 2011 17:13:33 +0200	[thread overview]
Message-ID: <4D25DC1D.1050604@redhat.com> (raw)
In-Reply-To: <AANLkTimN8=ji7y5Yb2CAU_S-v=bD-TdkmP6wR8RwhKeV@mail.gmail.com>

On 01/06/2011 03:53 PM, Duy Le (Dan) wrote:
> Hi there,
>
> I used a raw disk image to host a VM. I later used blktrace to capture
> write requests issued from the guest to commit data to a physical disk
> and found that the request size of the host is 8 blocks (4KB) larger
> than that of the guest. Here is a part of the trace.
>
> --- Guest
> 251,32   0      100     2.399993525    10  D   W 18747926 + 8 [kblockd/0]
> 251,32   0      101     2.399996297    10  D   W 18752462 + 24 [kblockd/0]
> 251,32   0      102     2.399998367    10  D   W 18756566 + 8 [kblockd/0]
>
> --- Host
>    8,16   0      155     2.415036111 32357  D   W 19146095 + 16 [kvm]
>    8,16   0      156     2.415042667 32357  D   W 19150639 + 32 [kvm]
>    8,16   0      158     2.415063867 32349  D   W 19154743 + 16 [kvm]
>
> The content of that additional written sectors on the disk can either
> be "zero" or something else. Please let me know if you have a clue or
> tell me which file in the package should I be looking at closer to
> understand this behavior.

Most likely your guest partitions are not aligned to a 4k boundary; this 
causes the host to add padding to the nearest 4k, which is consistent 
with what you saw.  You can use fdisk to confirm this.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2011-01-06 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 13:53 Host's write request is 4KB larger than that of the guest? Duy Le (Dan)
2011-01-06 15:13 ` Avi Kivity [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=4D25DC1D.1050604@redhat.com \
    --to=avi@redhat.com \
    --cc=duyle.vn@gmail.com \
    --cc=kvm@vger.kernel.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 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.