[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 01/16] migration: Don't use INT64_MAX for unlimited rate
|
From: |
Leonardo Brás |
|
Subject: |
Re: [PATCH v2 01/16] migration: Don't use INT64_MAX for unlimited rate |
|
Date: |
Mon, 22 May 2023 22:57:33 -0300 |
|
User-agent: |
Evolution 3.48.1 |
On Tue, 2023-05-16 at 14:47 +0200, Cédric Le Goater wrote:
> On 5/16/23 11:24, Juan Quintela wrote:
> > David Edmondson <david.edmondson@oracle.com> wrote:
> > > Juan Quintela <quintela@redhat.com> writes:
> > >
> > > > Define and use RATE_LIMIT_MAX instead.
> > >
> > > Suggest "RATE_LIMIT_MAX_NONE".
> >
> > Then even better
> >
> > RATE_LIMIT_DISABLED?
>
> I'd vote for RATE_LIMIT_DISABLED.
Me too.
>
> > RATE_LIMIT_NONE?
> >
> > Using MAX and NONE at the same time looks strange.
>
> Cheers,
>
> C.
>
Reviewed-by: Leonardo Bras <leobras@redhat.com>
[PATCH v2 02/16] migration: Correct transferred bytes value, Juan Quintela, 2023/05/15
[PATCH v2 03/16] migration: Move setup_time to mig_stats, Juan Quintela, 2023/05/15