search for: 5min12s

...ation, where the guest ceaselessy >> migrates between the source and destination. Linux compilation, >> i.e. make bzImage -j4, is performed during the Ping-Pong migration. The >> legacy case takes 5min14s to finish the compilation. With this >> optimization patched, it takes 5min12s. > How is migration time affected in this case? When the linux compilation workload runs, the migration time (both the legacy and this optimization case) varies as the compilation goes on. It seems not easy to give a static speedup number, some times the migration time is reduced to 33%, so...

...ation, where the guest ceaselessy >> migrates between the source and destination. Linux compilation, >> i.e. make bzImage -j4, is performed during the Ping-Pong migration. The >> legacy case takes 5min14s to finish the compilation. With this >> optimization patched, it takes 5min12s. > How is migration time affected in this case? When the linux compilation workload runs, the migration time (both the legacy and this optimization case) varies as the compilation goes on. It seems not easy to give a static speedup number, some times the migration time is reduced to 33%, so...

...- Guest with Linux Compilation Workload (make bzImage -j4): > > - Live Migration Time (average) > > Optimization v.s. Legacy = 1407ms v.s. 2528ms --> ~44% reduction > > - Linux Compilation Time > > Optimization v.s. Legacy = 5min4s v.s. 5min12s > > --> no obvious difference > > I'd like to see dgilbert's take on whether this kind of gain > justifies adding a PV interfaces, and what kind of guest workload > is appropriate. > > Cc'd. Well, 44% is great ... although the measurement is a bit...

...- Guest with Linux Compilation Workload (make bzImage -j4): > > - Live Migration Time (average) > > Optimization v.s. Legacy = 1402ms v.s. 2528ms --> ~44% reduction > > - Linux Compilation Time > > Optimization v.s. Legacy = 5min6s v.s. 5min12s > > --> no obvious difference > > > > Being in version 34 already, this whole thing still looks and feels like > a big hack to me. It might just be me, but especially if I read about > assumptions like "QEMU will not hotplug memory during migration"....

...- Guest with Linux Compilation Workload (make bzImage -j4): > > - Live Migration Time (average) > > Optimization v.s. Legacy = 1402ms v.s. 2528ms --> ~44% reduction > > - Linux Compilation Time > > Optimization v.s. Legacy = 5min6s v.s. 5min12s > > --> no obvious difference > > > > Being in version 34 already, this whole thing still looks and feels like > a big hack to me. It might just be me, but especially if I read about > assumptions like "QEMU will not hotplug memory during migration"....

...easelessy > > > migrates between the source and destination. Linux compilation, > > > i.e. make bzImage -j4, is performed during the Ping-Pong migration. The > > > legacy case takes 5min14s to finish the compilation. With this > > > optimization patched, it takes 5min12s. > > How is migration time affected in this case? > > > When the linux compilation workload runs, the migration time (both the > legacy and this optimization case) varies as the compilation goes on. It > seems not easy to give a static speedup number, some times the migration...

...on result) > - Guest with Linux Compilation Workload (make bzImage -j4): > - Live Migration Time (average) > Optimization v.s. Legacy = 1407ms v.s. 2528ms --> ~44% reduction > - Linux Compilation Time > Optimization v.s. Legacy = 5min4s v.s. 5min12s > --> no obvious difference > > ChangeLog: > v35->v36: > - remove the mm patch, as Linus has a suggestion to get free page > addresses via allocation, instead of reading from the free page > list. > - virtio-balloon: > - replac...

...on result) > - Guest with Linux Compilation Workload (make bzImage -j4): > - Live Migration Time (average) > Optimization v.s. Legacy = 1407ms v.s. 2528ms --> ~44% reduction > - Linux Compilation Time > Optimization v.s. Legacy = 5min4s v.s. 5min12s > --> no obvious difference I'd like to see dgilbert's take on whether this kind of gain justifies adding a PV interfaces, and what kind of guest workload is appropriate. Cc'd. > ChangeLog: > v35->v36: > - remove the mm patch, as Linus has a suggestio...

...ux Compilation Workload (make bzImage -j4): >>> - Live Migration Time (average) >>> Optimization v.s. Legacy = 1407ms v.s. 2528ms --> ~44% reduction >>> - Linux Compilation Time >>> Optimization v.s. Legacy = 5min4s v.s. 5min12s >>> --> no obvious difference >> I'd like to see dgilbert's take on whether this kind of gain >> justifies adding a PV interfaces, and what kind of guest workload >> is appropriate. >> >> Cc'd. > Well, 44% is great ... although the...

...ompilation Workload (make bzImage -j4): > > > - Live Migration Time (average) > > > Optimization v.s. Legacy = 1402ms v.s. 2528ms --> ~44% reduction > > > - Linux Compilation Time > > > Optimization v.s. Legacy = 5min6s v.s. 5min12s > > > --> no obvious difference > > > > > > > Being in version 34 already, this whole thing still looks and feels > > like a big hack to me. It might just be me, but especially if I read > > about assumptions like "QEMU will not hotplug me...

...e bzImage -j4): > > > > - Live Migration Time (average) > > > > Optimization v.s. Legacy = 1407ms v.s. 2528ms --> ~44% reduction > > > > - Linux Compilation Time > > > > Optimization v.s. Legacy = 5min4s v.s. 5min12s > > > > --> no obvious difference > > > I'd like to see dgilbert's take on whether this kind of gain > > > justifies adding a PV interfaces, and what kind of guest workload > > > is appropriate. > > > > > > Cc'd. &g...

...- Guest with Linux Compilation Workload (make bzImage -j4): >> - Live Migration Time (average) >> Optimization v.s. Legacy = 1402ms v.s. 2528ms --> ~44% reduction >> - Linux Compilation Time >> Optimization v.s. Legacy = 5min6s v.s. 5min12s >> --> no obvious difference >> > Being in version 34 already, this whole thing still looks and feels like > a big hack to me. It might just be me, but especially if I read about > assumptions like "QEMU will not hotplug memory during migration". This &g...

...- Guest with Linux Compilation Workload (make bzImage -j4): >> - Live Migration Time (average) >> Optimization v.s. Legacy = 1402ms v.s. 2528ms --> ~44% reduction >> - Linux Compilation Time >> Optimization v.s. Legacy = 5min6s v.s. 5min12s >> --> no obvious difference >> > Being in version 34 already, this whole thing still looks and feels like > a big hack to me. It might just be me, but especially if I read about > assumptions like "QEMU will not hotplug memory during migration". This &g...

...local live migration, where the guest ceaselessy > migrates between the source and destination. Linux compilation, > i.e. make bzImage -j4, is performed during the Ping-Pong migration. The > legacy case takes 5min14s to finish the compilation. With this > optimization patched, it takes 5min12s. How is migration time affected in this case? > ChangeLog: > v27->v28: > - mm/page_poison: Move PAGE_POISON to page_poison.c and add a function > to expose page poison val to kernel modules. > v26->v27: > - add a new patch to expose page_poisoning_enabled to...

...ect the comparison result) - Guest with Linux Compilation Workload (make bzImage -j4): - Live Migration Time (average) Optimization v.s. Legacy = 1407ms v.s. 2528ms --> ~44% reduction - Linux Compilation Time Optimization v.s. Legacy = 5min4s v.s. 5min12s --> no obvious difference ChangeLog: v35->v36: - remove the mm patch, as Linus has a suggestion to get free page addresses via allocation, instead of reading from the free page list. - virtio-balloon: - replace oom notifier with shrinker; - the g...

...ect the comparison result) - Guest with Linux Compilation Workload (make bzImage -j4): - Live Migration Time (average) Optimization v.s. Legacy = 1407ms v.s. 2528ms --> ~44% reduction - Linux Compilation Time Optimization v.s. Legacy = 5min4s v.s. 5min12s --> no obvious difference ChangeLog: v35->v36: - remove the mm patch, as Linus has a suggestion to get free page addresses via allocation, instead of reading from the free page list. - virtio-balloon: - replace oom notifier with shrinker; - the g...

...ux Compilation Workload (make bzImage -j4): >>> - Live Migration Time (average) >>> Optimization v.s. Legacy = 1402ms v.s. 2528ms --> ~44% reduction >>> - Linux Compilation Time >>> Optimization v.s. Legacy = 5min6s v.s. 5min12s >>> --> no obvious difference >>> >> Being in version 34 already, this whole thing still looks and feels like >> a big hack to me. It might just be me, but especially if I read about >> assumptions like "QEMU will not hotplug memory during migr...

...reduction > - Guest with Linux Compilation Workload (make bzImage -j4): > - Live Migration Time (average) > Optimization v.s. Legacy = 1402ms v.s. 2528ms --> ~44% reduction > - Linux Compilation Time > Optimization v.s. Legacy = 5min6s v.s. 5min12s > --> no obvious difference > Being in version 34 already, this whole thing still looks and feels like a big hack to me. It might just be me, but especially if I read about assumptions like "QEMU will not hotplug memory during migration". This does not feel like a cle...

...: Set up a Ping-Pong local live migration, where the guest ceaselessy migrates between the source and destination. Linux compilation, i.e. make bzImage -j4, is performed during the Ping-Pong migration. The legacy case takes 5min14s to finish the compilation. With this optimization patched, it takes 5min12s. ChangeLog: v27->v28: - mm/page_poison: Move PAGE_POISON to page_poison.c and add a function to expose page poison val to kernel modules. v26->v27: - add a new patch to expose page_poisoning_enabled to kernel modules - virtio-balloon: set poison_val to 0xaaaaaaaa, instead o...

...: Set up a Ping-Pong local live migration, where the guest ceaselessy migrates between the source and destination. Linux compilation, i.e. make bzImage -j4, is performed during the Ping-Pong migration. The legacy case takes 5min14s to finish the compilation. With this optimization patched, it takes 5min12s. ChangeLog: v27->v28: - mm/page_poison: Move PAGE_POISON to page_poison.c and add a function to expose page poison val to kernel modules. v26->v27: - add a new patch to expose page_poisoning_enabled to kernel modules - virtio-balloon: set poison_val to 0xaaaaaaaa, instead o...