qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Eyal Moscovici <eyal.moscovici@oracle.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	liran.alon@oracle.com, qemu-block@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH 0/2] Additional parameters for qemu_img map
Date: Wed, 29 Apr 2020 09:39:38 -0400	[thread overview]
Message-ID: <59b0896d-85ad-08b5-fcc1-36adad7501a4@redhat.com> (raw)
In-Reply-To: <20200322091117.79443-1-eyal.moscovici@oracle.com>

Hi, this series is 30 days old and didn't attract any replies. As the
5.0 release has just shipped, it may be re-appropriate to resubmit this
series for inclusion in the next release.

On 3/22/20 5:11 AM, Eyal Moscovici wrote:
> Hi,
> 
> The following series adds two parameters to qemu-img map:
> 1. start-offset: mapping starting offset.
> 2. max-length: the length of the mapping.
> 
> These parameters proved useful when mapping large disk spread across
> long store file chains. It allows us to bound the execution time of each
> qemu-img map execution as well as recover from failed mapping
> operations. In addition the map operation can divided to
> multiple independent tasks.
> 
> Eyal Moscovici (2):
>   qemu-img: refactor dump_map_entry JSON format output
>   qemu-img: Add --start-offset and --max-length to map
> 
>  docs/tools/qemu-img.rst |  2 +-
>  qemu-img-cmds.hx        |  4 ++--
>  qemu-img.c              | 42 ++++++++++++++++++++++++++++++++++++-----
>  3 files changed, 40 insertions(+), 8 deletions(-)
> 

-- 
—js



  parent reply	other threads:[~2020-04-29 13:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22  9:11 [PATCH 0/2] Additional parameters for qemu_img map Eyal Moscovici
2020-03-22  9:11 ` [PATCH 1/2] qemu-img: refactor dump_map_entry JSON format output Eyal Moscovici
2020-04-29 14:58   ` Eric Blake
2020-05-06  9:55     ` Eyal Moscovici
2020-03-22  9:11 ` [PATCH 2/2] qemu-img: Add --start-offset and --max-length to map Eyal Moscovici
2020-04-29 15:04   ` Eric Blake
2020-05-06  9:52     ` Eyal Moscovici
2020-04-29 13:39 ` John Snow [this message]
2020-05-06 21:34   ` [PATCH v2 0/5] Additional parameters for qemu_img map Eyal Moscovici
2020-05-06 21:34     ` [PATCH v2 1/5] qemu-img: remove check that cvtnum value > MAX_INT Eyal Moscovici
2020-05-06 21:49       ` Eric Blake
2020-05-12  9:39         ` Eyal Moscovici
2020-05-12 14:14           ` Eric Blake
2020-05-06 21:34     ` [PATCH v2 2/5] qemu_img: add error report to cvtnum Eyal Moscovici
2020-05-06 21:59       ` Eric Blake
2020-05-12  9:44         ` Eyal Moscovici
2020-05-06 21:34     ` [PATCH v2 3/5] qemu-img: validate image length in img_map Eyal Moscovici
2020-05-06 22:01       ` Eric Blake
2020-05-06 21:34     ` [PATCH v2 4/5] qemu-img: refactor dump_map_entry JSON format output Eyal Moscovici
2020-05-06 21:34     ` [PATCH v2 5/5] qemu-img: Add --start-offset and --max-length to map Eyal Moscovici
2020-05-06 22:04       ` Eric Blake
2020-05-12  9:48         ` Eyal Moscovici
2020-05-06 21:45     ` [PATCH v2 0/5] Additional parameters for qemu_img map Eric Blake

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=59b0896d-85ad-08b5-fcc1-36adad7501a4@redhat.com \
    --to=jsnow@redhat.com \
    --cc=eyal.moscovici@oracle.com \
    --cc=kwolf@redhat.com \
    --cc=liran.alon@oracle.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.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).