[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <F2CBF3009FA73547804AE4C663CAB28E0421A844@shsmsx102.ccr.corp.intel.com>
Date: Tue, 9 Aug 2016 02:52:41 +0000
From: "Li, Liang Z" <liang.z.li@...el.com>
To: "Hansen, Dave" <dave.hansen@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"virtio-dev@...ts.oasis-open.org" <virtio-dev@...ts.oasis-open.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"qemu-devel@...gnu.org" <qemu-devel@...gnu.org>,
"quintela@...hat.com" <quintela@...hat.com>,
"dgilbert@...hat.com" <dgilbert@...hat.com>
Subject: RE: [PATCH v3 kernel 0/7] Extend virtio-balloon for fast
(de)inflating & fast live migration
> Subject: Re: [PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating
> & fast live migration
>
> On 08/07/2016 11:35 PM, Liang Li wrote:
> > Dave Hansen suggested a new scheme to encode the data structure,
> > because of additional complexity, it's not implemented in v3.
>
> FWIW, I don't think it takes any additional complexity here, at least in the
> guest implementation side. The thing I suggested would just mean explicitly
> calling out that there was a single bitmap instead of implying it in the ABI.
>
> Do you think the scheme I suggested is the way to go?
Yes, I think so. And I will do that in the later version. In this V3, I just want to solve the
issue caused by a large page bitmap in v2.
Liang
Powered by blists - more mailing lists