From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, shadowsor@gmail.com,
famz@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCHv3] block: introduce BDRV_O_SEQUENTIAL
Date: Wed, 14 May 2014 11:31:11 -0600 [thread overview]
Message-ID: <5373A85F.9080201@redhat.com> (raw)
In-Reply-To: <1399984592-2469-1-git-send-email-pl@kamp.de>
[-- Attachment #1: Type: text/plain, Size: 1975 bytes --]
On 05/13/2014 06:36 AM, Peter Lieven wrote:
> this patch introduces a new flag to indicate that we are going to sequentially
> read from a file and do not plan to reread/reuse the data after it has been read.
>
> The current use of this flag is to open the source(s) of a qemu-img convert
> process. If a protocol from block/raw-posix.c is used posix_fadvise is utilized
> to advise to the kernel that we are going to read sequentially from the
> file and a POSIX_FADV_DONTNEED advise is issued after each write to indicate
> that there is no advantage keeping the blocks in the buffers.
>
> Consider the following test case that was created to confirm the behaviour of
> the new flag:
>
> A 10G logical volume was created and filled with random data.
> Then the logical volume was exported via qemu-img convert to an iscsi target.
> Before the export was started all caches of the linux kernel where dropped.
>
> Old behavior:
> - The convert process took 3m45s and the buffer cache grew up to 9.67 GB close
> to the end of the conversion. After qemu-img terminated all the buffers were
> freed by the kernel.
>
> New behavior with the -N switch:
> - The convert process took 3m43s and the buffer cache grew up to 15.48 MB close
> to the end with some small peaks up to 30 MB during the conversion.
>
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> v2->v3: - rebased
> - fixed typo in commit msg [Fam]
> v1->v2: - added test example to commit msg
> - added -N knob to qemu-img
>
> block/raw-posix.c | 14 ++++++++++++++
> include/block/block.h | 1 +
> qemu-img-cmds.hx | 4 ++--
> qemu-img.c | 15 ++++++++++++---
> qemu-img.texi | 9 ++++++++-
> 5 files changed, 37 insertions(+), 6 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2014-05-14 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 12:36 [Qemu-devel] [PATCHv3] block: introduce BDRV_O_SEQUENTIAL Peter Lieven
2014-05-14 17:31 ` Eric Blake [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=5373A85F.9080201@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=shadowsor@gmail.com \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).