On Fri, Apr 03, 2015 at 12:25:14PM +0800, Xiao Guangrong wrote:
>
>
>On 03/30/2015 07:48 AM, Wanpeng Li wrote:
>>There are two scenarios for the requirement of collapsing small sptes
>>into large sptes.
>>- dirty logging tracks sptes in 4k granularity, so large sptes are splitted,
>> the large
On Fri, Apr 03, 2015 at 12:25:14PM +0800, Xiao Guangrong wrote:
On 03/30/2015 07:48 AM, Wanpeng Li wrote:
There are two scenarios for the requirement of collapsing small sptes
into large sptes.
- dirty logging tracks sptes in 4k granularity, so large sptes are splitted,
the large sptes will
On 03/30/2015 07:48 AM, Wanpeng Li wrote:
There are two scenarios for the requirement of collapsing small sptes
into large sptes.
- dirty logging tracks sptes in 4k granularity, so large sptes are splitted,
the large sptes will be reallocated in the destination machine and the
guest in
On 03/30/2015 07:48 AM, Wanpeng Li wrote:
There are two scenarios for the requirement of collapsing small sptes
into large sptes.
- dirty logging tracks sptes in 4k granularity, so large sptes are splitted,
the large sptes will be reallocated in the destination machine and the
guest in
There are two scenarios for the requirement of collapsing small sptes
into large sptes.
- dirty logging tracks sptes in 4k granularity, so large sptes are splitted,
the large sptes will be reallocated in the destination machine and the
guest in the source machine will be destroyed when live
There are two scenarios for the requirement of collapsing small sptes
into large sptes.
- dirty logging tracks sptes in 4k granularity, so large sptes are splitted,
the large sptes will be reallocated in the destination machine and the
guest in the source machine will be destroyed when live
6 matches
Mail list logo
