Peter Xu writes:
> On Fri, Aug 04, 2023 at 02:06:02PM +0200, Markus Armbruster wrote:
>> Peter Xu writes:
>>
>> > On Wed, Jul 26, 2023 at 08:21:35AM +0200, Markus Armbruster wrote:
>> >> Peter Xu writes:
>> >>
>> >> > Hi, Markus,
>> >> >
>> >> > On Tue, Jul 25, 2023 at 01:10:01PM +0200, Marku
Peter Xu writes:
> On Fri, Aug 04, 2023 at 02:39:15PM +0100, Daniel P. Berrangé wrote:
>> On Wed, Jul 26, 2023 at 11:12:31AM -0400, Peter Xu wrote:
>> > On Wed, Jul 26, 2023 at 08:21:35AM +0200, Markus Armbruster wrote:
>> > > Peter Xu writes:
>> > >
>> > > > Hi, Markus,
>> > > >
>> > > > On Tu
On Fri, Aug 04, 2023 at 02:39:15PM +0100, Daniel P. Berrangé wrote:
> On Wed, Jul 26, 2023 at 11:12:31AM -0400, Peter Xu wrote:
> > On Wed, Jul 26, 2023 at 08:21:35AM +0200, Markus Armbruster wrote:
> > > Peter Xu writes:
> > >
> > > > Hi, Markus,
> > > >
> > > > On Tue, Jul 25, 2023 at 01:10:01P
On Wed, Jul 26, 2023 at 11:12:31AM -0400, Peter Xu wrote:
> On Wed, Jul 26, 2023 at 08:21:35AM +0200, Markus Armbruster wrote:
> > Peter Xu writes:
> >
> > > Hi, Markus,
> > >
> > > On Tue, Jul 25, 2023 at 01:10:01PM +0200, Markus Armbruster wrote:
> >
> > [...]
> >
> > >> For better or worse,
On Fri, Aug 04, 2023 at 02:06:02PM +0200, Markus Armbruster wrote:
> Peter Xu writes:
>
> > On Wed, Jul 26, 2023 at 08:21:35AM +0200, Markus Armbruster wrote:
> >> Peter Xu writes:
> >>
> >> > Hi, Markus,
> >> >
> >> > On Tue, Jul 25, 2023 at 01:10:01PM +0200, Markus Armbruster wrote:
> >>
> >
Peter Xu writes:
> On Wed, Jul 26, 2023 at 08:21:35AM +0200, Markus Armbruster wrote:
>> Peter Xu writes:
>>
>> > Hi, Markus,
>> >
>> > On Tue, Jul 25, 2023 at 01:10:01PM +0200, Markus Armbruster wrote:
>>
>> [...]
>>
>> >> For better or worse, we duplicate full documentation between
>> >> Mi
On Tue, Jul 25, 2023 at 06:10:18PM +0100, Daniel P. Berrangé wrote:
> On Tue, Jul 25, 2023 at 12:38:23PM -0400, Peter Xu wrote:
> > I see you used "convergance" explicitly even after PeterM's reply, is that
> > what you prefer over "convergence"? I do see more occurances of
> > "convergence" as a
On Wed, Jul 26, 2023 at 08:21:35AM +0200, Markus Armbruster wrote:
> Peter Xu writes:
>
> > Hi, Markus,
> >
> > On Tue, Jul 25, 2023 at 01:10:01PM +0200, Markus Armbruster wrote:
>
> [...]
>
> >> For better or worse, we duplicate full documentation between
> >> MigrationParameter, MigrateSetPar
Peter Xu writes:
> Hi, Markus,
>
> On Tue, Jul 25, 2023 at 01:10:01PM +0200, Markus Armbruster wrote:
[...]
>> For better or worse, we duplicate full documentation between
>> MigrationParameter, MigrateSetParameters, and MigrationParameters. This
>> would be the first instance where we referen
On Tue, Jul 25, 2023 at 12:38:23PM -0400, Peter Xu wrote:
> I see you used "convergance" explicitly even after PeterM's reply, is that
> what you prefer over "convergence"? I do see more occurances of
> "convergence" as a word in migration context, though.
Ignore my speling erors :-)
>
Hi, Markus,
On Tue, Jul 25, 2023 at 01:10:01PM +0200, Markus Armbruster wrote:
> Peter Xu writes:
>
> > Migration bandwidth is a very important value to live migration. It's
> > because it's one of the major factors that we'll make decision on when to
> > switchover to destination in a precopy
On Tue, Jul 25, 2023 at 05:09:57PM +0100, Daniel P. Berrangé wrote:
> On Tue, Jul 25, 2023 at 11:54:52AM -0400, Peter Xu wrote:
> > We can make the semantics specific, no strong opinion here. I wished it
> > can be as generic / easy as possible but maybe I went too far.
> >
> > Though, is there a
On Tue, Jul 25, 2023 at 11:54:52AM -0400, Peter Xu wrote:
> We can make the semantics specific, no strong opinion here. I wished it
> can be as generic / easy as possible but maybe I went too far.
>
> Though, is there anything else we can choose from besides
> "max-convergence-bandwidth"? Or am I
On Tue, Jul 25, 2023 at 10:16:52AM +0100, Daniel P. Berrangé wrote:
> On Mon, Jul 24, 2023 at 03:47:50PM -0400, Peter Xu wrote:
> > On Mon, Jul 24, 2023 at 07:04:29PM +0100, Daniel P. Berrangé wrote:
> > > On Mon, Jul 24, 2023 at 01:07:55PM -0400, Peter Xu wrote:
> > > > Migration bandwidth is a ve
Peter Xu writes:
> Migration bandwidth is a very important value to live migration. It's
> because it's one of the major factors that we'll make decision on when to
> switchover to destination in a precopy process.
>
> This value is currently estimated by QEMU during the whole live migration
> p
On Mon, Jul 24, 2023 at 03:47:50PM -0400, Peter Xu wrote:
> On Mon, Jul 24, 2023 at 07:04:29PM +0100, Daniel P. Berrangé wrote:
> > On Mon, Jul 24, 2023 at 01:07:55PM -0400, Peter Xu wrote:
> > > Migration bandwidth is a very important value to live migration. It's
> > > because it's one of the ma
On Mon, Jul 24, 2023 at 07:04:29PM +0100, Daniel P. Berrangé wrote:
> On Mon, Jul 24, 2023 at 01:07:55PM -0400, Peter Xu wrote:
> > Migration bandwidth is a very important value to live migration. It's
> > because it's one of the major factors that we'll make decision on when to
> > switchover to
On Mon, 24 Jul 2023 at 19:05, Daniel P. Berrangé wrote:
>
> I feel like rather than "available-bandwidth", we should call
> it "max-convergance-bandwidth".
"convergence" (I mention only since it's a proposed
user-visible bit of API :-)
-- PMM
On Mon, Jul 24, 2023 at 01:07:55PM -0400, Peter Xu wrote:
> Migration bandwidth is a very important value to live migration. It's
> because it's one of the major factors that we'll make decision on when to
> switchover to destination in a precopy process.
To elaborate on this for those reading al
Migration bandwidth is a very important value to live migration. It's
because it's one of the major factors that we'll make decision on when to
switchover to destination in a precopy process.
This value is currently estimated by QEMU during the whole live migration
process by monitoring how fast
20 matches
Mail list logo
