From: Gerd Hoffmann <kraxel@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Break down the MTP write operation
Date: Tue, 8 Jan 2019 12:59:20 +0100 [thread overview]
Message-ID: <20190108115920.kmtuxtlxabgajl6f@sirius.home.kraxel.org> (raw)
In-Reply-To: <20181115220132.6531-1-bsd@redhat.com>
Hi,
> For larger files, not only do we keep reallocating to increase the mtp buffer
> size, the write also happens in one go. This does two things:
>
> Write to file upto a certain data size we have received so far and second,
> reuse the buffer again instead of reallocating to a larger buffer size.
>
> Tested with different file sizes on a Linux guest.
Doesn't apply to master, please rebase.
thanks,
Gerd
prev parent reply other threads:[~2019-01-08 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 22:01 [Qemu-devel] [PATCH 0/2] Break down the MTP write operation Bandan Das
2018-11-15 22:01 ` [Qemu-devel] [PATCH 1/2] usb-mtp: Reallocate buffer in multiples of MTP_WRITE_BUF_SZ Bandan Das
2018-11-15 22:01 ` [Qemu-devel] [PATCH 2/2] usb-mtp: breakup MTP write into smaller chunks Bandan Das
2019-01-08 11:59 ` Gerd Hoffmann [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=20190108115920.kmtuxtlxabgajl6f@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=bsd@redhat.com \
--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).