On Fri, Aug 25, 2017 at 10:34:56AM +0100, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > On Wed, Aug 23, 2017 at 07:01:35PM +0100, Dr. David Alan Gilbert wrote:
> > > * Peter Xu (pet...@redhat.com) wrote:
> > > > Now at least migrate_incoming can be run in parallel. Let'
* Peter Xu (pet...@redhat.com) wrote:
> On Wed, Aug 23, 2017 at 07:01:35PM +0100, Dr. David Alan Gilbert wrote:
> > * Peter Xu (pet...@redhat.com) wrote:
> > > Now at least migrate_incoming can be run in parallel. Let's provide a
> > > migration lock to protect it.
> > >
> > > Signed-off-by: Pete
On Wed, Aug 23, 2017 at 07:01:35PM +0100, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > Now at least migrate_incoming can be run in parallel. Let's provide a
> > migration lock to protect it.
> >
> > Signed-off-by: Peter Xu
> > ---
> > migration/migration.c | 6 +
* Peter Xu (pet...@redhat.com) wrote:
> Now at least migrate_incoming can be run in parallel. Let's provide a
> migration lock to protect it.
>
> Signed-off-by: Peter Xu
> ---
> migration/migration.c | 6 ++
> migration/migration.h | 3 +++
> 2 files changed, 9 insertions(+)
>
> diff --git
Now at least migrate_incoming can be run in parallel. Let's provide a
migration lock to protect it.
Signed-off-by: Peter Xu
---
migration/migration.c | 6 ++
migration/migration.h | 3 +++
2 files changed, 9 insertions(+)
diff --git a/migration/migration.c b/migration/migration.c
index c3f
