qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] buffer alignment for block backends
Date: Thu, 9 Apr 2009 18:13:02 +0200	[thread overview]
Message-ID: <20090409161301.GK5457@const.bordeaux.inria.fr> (raw)
In-Reply-To: <49DE193B.50703@redhat.com>

Gerd Hoffmann, le Thu 09 Apr 2009 17:50:19 +0200, a écrit :
> On 04/09/09 17:21, Samuel Thibault wrote:
> >Gerd Hoffmann, le Thu 09 Apr 2009 15:54:34 +0200, a écrit :
> >>On 04/09/09 15:30, Stefano Stabellini wrote:
> >>>The userspace\kernelspace distinction does not make much sense in
> >>>minios, but yes it provides an interface to communicate with blkback in
> >>>dom0. This interface is used by block-vbd in qemu instead of
> >>>block-raw-posix when run in minios.
> >>Sit back, look again.  Do you really need it being page-aligned?
> >
> >Page aligned is an optimization which comes for free when you can
> >already choose the alignment.
> 
> Ok, so you don't have to.
> 
> Does it have an effect positive actually?  i.e. do you have requests 
> which would fit into one page but actually span two due to the misalignment?

I/O with small files often fit in just one page. If they're never
aligned the amount of grants to transfer is doubled.

> At least when watching the linux kernel access pattern I see larger 
> requests being page aligned anyway.
> Probably page cache reads and writes.

Yes, that's what I meant in another mail. Usually, I/O will already be
aligned.  That's not a reason for not trying to optimize other cases.

Samuel

  parent reply	other threads:[~2009-04-09 16:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 13:35 [Qemu-devel] buffer alignment for block backends Stefano Stabellini
2009-04-08 18:53 ` Anthony Liguori
2009-04-09  9:57   ` Stefano Stabellini
2009-04-09 13:11     ` Anthony Liguori
2009-04-09 13:30       ` Stefano Stabellini
2009-04-09 13:54         ` Gerd Hoffmann
2009-04-09 15:21           ` Samuel Thibault
2009-04-09 15:46             ` Stefano Stabellini
2009-04-09 15:50             ` Gerd Hoffmann
2009-04-09 16:11               ` Stefano Stabellini
2009-04-09 16:13               ` Samuel Thibault [this message]
2009-04-09 16:28               ` Anthony Liguori
2009-04-09 15:55             ` Jamie Lokier
2009-04-09 16:15               ` Samuel Thibault
2009-04-09 17:29               ` Lennart Sorensen
2009-04-09 13:33       ` Stefano Stabellini
2009-04-09 15:19       ` Samuel Thibault
2009-04-09 15:38         ` Paul Brook
2009-04-09 15:40           ` Samuel Thibault
2009-04-09 15:56         ` Anthony Liguori
2009-04-09 16:19           ` Samuel Thibault
2009-04-09 10:07   ` Stefano Stabellini
2009-04-09 13:14     ` Anthony Liguori
2009-04-09 13:30       ` Stefano Stabellini
2009-04-09 13:19     ` Christoph Hellwig
2009-04-09 13:30       ` Stefano Stabellini
2009-04-09 15:31         ` Christoph Hellwig

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=20090409161301.GK5457@const.bordeaux.inria.fr \
    --to=samuel.thibault@ens-lyon.org \
    --cc=qemu-devel@nongnu.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).