From: "Denis V. Lunev" <den@openvz.org>
To: Peter Lieven <pl@kamp.de>,
"Denis V. Lunev" <den-lists@parallels.com>,
qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@redhat.com,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block: limited request size in write zeroes unsupported path
Date: Mon, 5 Jan 2015 15:28:41 +0300 [thread overview]
Message-ID: <54AA8379.4020206@openvz.org> (raw)
In-Reply-To: <54AA8038.7090608@kamp.de>
On 05/01/15 15:14, Peter Lieven wrote:
> On 05.01.2015 12:51, Denis V. Lunev wrote:
>> On 05/01/15 14:29, Peter Lieven wrote:
>>> If bs->bl.max_write_zeroes is large and we end up in the unsupported
>>> path we might allocate a lot of memory for the iovector and/or even
>>> generate an oversized requests.
>>>
>>> Fix this by limiting the request by the minimum of the reported
>>> maximum transfer size or 16MB (32768 sectors).
>>>
>>> Reported-by: Denis V. Lunev <den@openvz.org>
>>> Signed-off-by: Peter Lieven <pl@kamp.de>
>>> ---
>>> block.c | 5 ++++-
>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/block.c b/block.c
>>> index a612594..8009478 100644
>>> --- a/block.c
>>> +++ b/block.c
>>> @@ -3203,6 +3203,9 @@ static int coroutine_fn
>>> bdrv_co_do_write_zeroes(BlockDriverState *bs,
>>>
>>> if (ret == -ENOTSUP) {
>>> /* Fall back to bounce buffer if write zeroes is
>>> unsupported */
>>> + int max_xfer_len =
>>> MIN_NON_ZERO(bs->bl.max_transfer_length,
>>> + MAX_WRITE_ZEROES_DEFAULT);
>>> + num = MIN(num, max_xfer_len);
>>> iov.iov_len = num * BDRV_SECTOR_SIZE;
>>> if (iov.iov_base == NULL) {
>>> iov.iov_base = qemu_try_blockalign(bs, num *
>>> BDRV_SECTOR_SIZE);
>>> @@ -3219,7 +3222,7 @@ static int coroutine_fn
>>> bdrv_co_do_write_zeroes(BlockDriverState *bs,
>>> /* Keep bounce buffer around if it is big enough for all
>>> * all future requests.
>>> */
>>> - if (num < max_write_zeroes) {
>>> + if (num < max_xfer_len) {
>>> qemu_vfree(iov.iov_base);
>>> iov.iov_base = NULL;
>>> }
>>>
>> this is not going to work IMHO. num is the number in sectors.
>> max_xfer_len is in bytes.
>
> bs->bl.max_transfer_length is in sectors.
>
> Peter
>
oops. you are right...
next prev parent reply other threads:[~2015-01-05 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 11:29 [Qemu-devel] [PATCH] block: limited request size in write zeroes unsupported path Peter Lieven
2015-01-05 11:51 ` Denis V. Lunev
2015-01-05 12:14 ` Peter Lieven
2015-01-05 12:28 ` Denis V. Lunev [this message]
2015-01-05 12:34 ` Denis V. Lunev
2015-01-06 15:43 ` Stefan Hajnoczi
2015-01-06 17:56 ` Denis V. Lunev
2015-01-06 15:42 ` Stefan Hajnoczi
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=54AA8379.4020206@openvz.org \
--to=den@openvz.org \
--cc=den-lists@parallels.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--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 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.