From: Kevin Wolf <kwolf@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org, stefanha@gmail.com,
ct@flyingcircus.io, mreitz@redhat.com, famz@redhat.com
Subject: Re: [Qemu-devel] [PATCH V2] qemu-img: make convert async
Date: Tue, 28 Feb 2017 11:30:42 +0100 [thread overview]
Message-ID: <20170228103042.GA4090@noname.redhat.com> (raw)
In-Reply-To: <11860d28-91e1-3858-e5f6-4176e9f72816@kamp.de>
Am 28.02.2017 um 10:59 hat Peter Lieven geschrieben:
> Am 27.02.2017 um 22:09 schrieb Eric Blake:
> >On 02/27/2017 05:03 AM, Peter Lieven wrote:
> >>the convert process is currently completely implemented with sync operations.
> >>That means it reads one buffer and then writes it. No parallelism and each sync
> >>request takes as long as it takes until it is completed.
> >>
> >>This patches introduces 2 new cmdline parameters. The -m parameter to specify
> >>the number of coroutines running in parallel (defaults to 8). And the -W paremeter to
> >s/paremeter/parameter/
> >
> >>allow qemu-img to write to the target out of order rather than sequential. This improves
> >>performance as the writes do not have to wait for each other to complete.
> >>
> >>Signed-off-by: Peter Lieven <pl@kamp.de>
> >>---
> >>@@ -1798,7 +1908,7 @@ static int img_convert(int argc, char **argv)
> >> {"image-opts", no_argument, 0, OPTION_IMAGE_OPTS},
> >> {0, 0, 0, 0}
> >> };
> >>- c = getopt_long(argc, argv, "hf:O:B:ce6o:s:l:S:pt:T:qn",
> >>+ c = getopt_long(argc, argv, "hf:O:B:ce6o:s:l:S:pt:T:qnm:W",
> >> long_options, NULL);
> >> if (c == -1) {
> >> break;
> >>@@ -1890,6 +2000,18 @@ static int img_convert(int argc, char **argv)
> >> case 'n':
> >> skip_create = 1;
> >> break;
> >>+ case 'm':
> >>+ num_coroutines = atoi(optarg);
> >atoi() should be avoided. It has no error checking, so it treats '-m 1'
> >and '-m 1k' identically. You are a bit justified in that '-m junk' gets
> >treated like '-m 0' and rejected, but it's still a poor error message in
> >that case.
>
> would you use qemu_strtoul or parse_uint instead?
>
> Kevin, shall I send a V3?
If you can send a v3 today, I'll replace the patch in my queue with it.
Otherwise we'll fix it on top during the freeze.
Kevin
prev parent reply other threads:[~2017-02-28 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 11:03 [Qemu-devel] [PATCH V2] qemu-img: make convert async Peter Lieven
2017-02-27 13:32 ` Stefan Hajnoczi
2017-02-27 20:37 ` Kevin Wolf
2017-02-27 21:09 ` Eric Blake
2017-02-28 9:59 ` Peter Lieven
2017-02-28 10:30 ` 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=20170228103042.GA4090@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=ct@flyingcircus.io \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=mreitz@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).