From: Matthew Wilcox <willy@infradead.org>
To: Wei Wang <wei.w.wang@intel.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org,
qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, linux-mm@kvack.org,
Liang Li <liang.z.li@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Amit Shah <amit.shah@redhat.com>,
Dave Hansen <dave.hansen@intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
David Hildenbrand <david@redhat.com>,
Liang Li <liliang324@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER
Date: Sat, 11 Mar 2017 06:09:47 -0800 [thread overview]
Message-ID: <20170311140946.GA1860@bombadil.infradead.org> (raw)
In-Reply-To: <58C3E6A3.1000000@intel.com>
On Sat, Mar 11, 2017 at 07:59:31PM +0800, Wei Wang wrote:
> I'm thinking what if the guest needs to transfer these much physically
> continuous
> memory to host: 1GB+2MB+64KB+32KB+16KB+4KB.
> Is it going to use Six 64-bit chunks? Would it be simpler if we just
> use the 128-bit chunk format (we can drop the previous normal 64-bit
> format)?
Is that a likely thing for the guest to need to do though? Freeing a
1GB page is much more liikely, IMO.
next prev parent reply other threads:[~2017-03-11 14:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 5:40 [Qemu-devel] [PATCH v7 kernel 0/5] Extend virtio-balloon for fast (de)inflating & fast live migration Wei Wang
2017-03-03 5:40 ` [Qemu-devel] [PATCH v7 kernel 1/5] virtio-balloon: rework deflate to add page to a list Wei Wang
2017-03-03 5:40 ` [Qemu-devel] [PATCH v7 kernel 2/5] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER Wei Wang
2017-03-08 4:01 ` Michael S. Tsirkin
2017-03-09 7:12 ` Wei Wang
2017-03-03 5:40 ` [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER Wei Wang
2017-03-08 4:01 ` Michael S. Tsirkin
2017-03-10 10:02 ` [Qemu-devel] [virtio-dev] " Wei Wang
2017-03-10 13:26 ` David Hildenbrand
2017-03-10 15:37 ` Michael S. Tsirkin
2017-03-09 14:14 ` [Qemu-devel] " Matthew Wilcox
2017-03-10 11:37 ` Wei Wang
2017-03-10 15:58 ` Michael S. Tsirkin
2017-03-10 17:11 ` Matthew Wilcox
2017-03-10 19:10 ` Michael S. Tsirkin
2017-03-10 21:18 ` Matthew Wilcox
2017-03-10 19:35 ` Michael S. Tsirkin
2017-03-10 21:25 ` Matthew Wilcox
2017-03-12 0:05 ` Michael S. Tsirkin
2017-03-11 11:59 ` Wei Wang
2017-03-11 14:09 ` Matthew Wilcox [this message]
2017-03-12 1:59 ` Wang, Wei W
2017-03-12 4:04 ` Michael S. Tsirkin
2017-03-13 12:41 ` Wang, Wei W
2017-03-12 0:07 ` Michael S. Tsirkin
2017-03-03 5:40 ` [Qemu-devel] [PATCH v7 kernel 4/5] virtio-balloon: define flags and head for host request vq Wei Wang
2017-03-08 4:02 ` Michael S. Tsirkin
2017-03-03 5:40 ` [Qemu-devel] [PATCH v7 kernel 5/5] This patch contains two parts: Wei Wang
2017-03-06 13:23 ` David Hildenbrand
2017-03-09 7:04 ` Wei Wang
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=20170311140946.GA1860@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=aarcange@redhat.com \
--cc=amit.shah@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=liang.z.li@intel.com \
--cc=liliang324@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wei.w.wang@intel.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).