All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Li Zhi Hui <zhihuili@linux.vnet.ibm.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2] block: Use bdrv functions to replace file operation in qcow.c
Date: Tue, 24 Jan 2012 14:45:06 +0100	[thread overview]
Message-ID: <4F1EB5E2.3000701@redhat.com> (raw)
In-Reply-To: <1321861239-15253-1-git-send-email-zhihuili@linux.vnet.ibm.com>

Am 21.11.2011 08:40, schrieb Li Zhi Hui:
> Since common file operation functions lack of error detection and use much more I/O syscalls, 
> so change them to bdrv series functions and reduce I/O request.
> 
> v2: avoid malloc a large memory
> v1: convert file operation functions to bdrv functions and reduce I/O request.
> 
> Signed-off-by: Li Zhi Hui <zhihuili@linux.vnet.ibm.com>

Thanks, applied to the block branch.

Kevin

      reply	other threads:[~2012-01-24 13:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  7:40 [Qemu-devel] [PATCH v2] block: Use bdrv functions to replace file operation in qcow.c Li Zhi Hui
2012-01-24 13:45 ` Kevin Wolf [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=4F1EB5E2.3000701@redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=zhihuili@linux.vnet.ibm.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 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.