From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org, jsnow@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 6/6] block/block-copy: increase buffered copy request
Date: Tue, 22 Oct 2019 12:36:44 +0200 [thread overview]
Message-ID: <5bbcd4bb-2131-d2ad-4bc6-3a69b5e1f992@redhat.com> (raw)
In-Reply-To: <20191016170905.8325-7-vsementsov@virtuozzo.com>
[-- Attachment #1.1: Type: text/plain, Size: 436 bytes --]
On 16.10.19 19:09, Vladimir Sementsov-Ogievskiy wrote:
> No reason to limit buffered copy to one cluster. Let's allow up to 1
> MiB.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> include/block/block-copy.h | 2 +-
> block/block-copy.c | 48 +++++++++++++++++++++++++-------------
> 2 files changed, 33 insertions(+), 17 deletions(-)
Reviewed-by: Max Reitz <mreitz@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-10-22 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 17:08 [PATCH v2 0/6] block-copy: memory limit Vladimir Sementsov-Ogievskiy
2019-10-16 17:09 ` [PATCH v2 1/6] block/block-copy: allocate buffer in block_copy_with_bounce_buffer Vladimir Sementsov-Ogievskiy
2019-10-16 17:09 ` [PATCH v2 2/6] block/block-copy: limit copy_range_size to 16 MiB Vladimir Sementsov-Ogievskiy
2019-10-16 17:09 ` [PATCH v2 3/6] block/block-copy: refactor copying Vladimir Sementsov-Ogievskiy
2019-10-22 9:53 ` Max Reitz
2019-10-16 17:09 ` [PATCH v2 4/6] util: introduce SharedResource Vladimir Sementsov-Ogievskiy
2019-10-22 10:23 ` Max Reitz
2019-10-22 10:59 ` Vladimir Sementsov-Ogievskiy
2019-10-16 17:09 ` [PATCH v2 5/6] block/block-copy: add memory limit Vladimir Sementsov-Ogievskiy
2019-10-22 10:30 ` Max Reitz
2019-10-16 17:09 ` [PATCH v2 6/6] block/block-copy: increase buffered copy request Vladimir Sementsov-Ogievskiy
2019-10-22 10:36 ` Max Reitz [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=5bbcd4bb-2131-d2ad-4bc6-3a69b5e1f992@redhat.com \
--to=mreitz@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).