From: Leon Romanovsky <leon@kernel•org>
To: Alex Williamson <alex.williamson@redhat•com>
Cc: Yishai Hadas <yishaih@nvidia•com>,
jgg@nvidia•com, saeedm@nvidia•com, kvm@vger•kernel.org,
netdev@vger•kernel.org, kuba@kernel•org, maorg@nvidia•com,
cohuck@redhat•com
Subject: Re: [PATCH V2 mlx5-next 0/4] Improve mlx5 live migration driver
Date: Wed, 11 May 2022 09:40:37 +0300 [thread overview]
Message-ID: <YntaZcd+Qv5UiQRN@unreal> (raw)
In-Reply-To: <20220510090053.56efd550.alex.williamson@redhat.com>
On Tue, May 10, 2022 at 09:00:53AM -0600, Alex Williamson wrote:
> On Tue, 10 May 2022 16:16:16 +0300
> Leon Romanovsky <leon@kernel•org> wrote:
>
> > On Tue, May 10, 2022 at 12:02:02PM +0300, Yishai Hadas wrote:
> > > This series improves mlx5 live migration driver in few aspects as of
> > > below.
> > >
> > > Refactor to enable running migration commands in parallel over the PF
> > > command interface.
> > >
> > > To achieve that we exposed from mlx5_core an API to let the VF be
> > > notified before that the PF command interface goes down/up. (e.g. PF
> > > reload upon health recovery).
> > >
> > > Once having the above functionality in place mlx5 vfio doesn't need any
> > > more to obtain the global PF lock upon using the command interface but
> > > can rely on the above mechanism to be in sync with the PF.
> > >
> > > This can enable parallel VFs migration over the PF command interface
> > > from kernel driver point of view.
> > >
> > > In addition,
> > > Moved to use the PF async command mode for the SAVE state command.
> > > This enables returning earlier to user space upon issuing successfully
> > > the command and improve latency by let things run in parallel.
> > >
> > > Alex, as this series touches mlx5_core we may need to send this in a
> > > pull request format to VFIO to avoid conflicts before acceptance.
> >
> > The PR was sent.
> > https://lore.kernel.org/netdev/20220510131236.1039430-1-leon@kernel.org/T/#u
>
> For patches 2-4, please add:
>
> Reviewed-by: Alex Williamson <alex.williamson@redhat•com>
Done, I force pushed same branch and tag, so previous PR is still valid
to be pulled.
https://lore.kernel.org/kvm/20220510131236.1039430-1-leon@kernel.org/T/#u
Thanks
>
> Thanks,
> Alex
>
next prev parent reply other threads:[~2022-05-11 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:02 [PATCH V2 mlx5-next 0/4] Improve mlx5 live migration driver Yishai Hadas
2022-05-10 9:02 ` [PATCH V2 mlx5-next 1/4] net/mlx5: Expose mlx5_sriov_blocking_notifier_register / unregister APIs Yishai Hadas
2022-05-10 9:02 ` [PATCH V2 mlx5-next 2/4] vfio/mlx5: Manage the VF attach/detach callback from the PF Yishai Hadas
2022-05-10 9:02 ` [PATCH V2 mlx5-next 3/4] vfio/mlx5: Refactor to enable VFs migration in parallel Yishai Hadas
2022-05-10 9:02 ` [PATCH V2 mlx5-next 4/4] vfio/mlx5: Run the SAVE state command in an async mode Yishai Hadas
2022-05-10 13:16 ` [PATCH V2 mlx5-next 0/4] Improve mlx5 live migration driver Leon Romanovsky
2022-05-10 15:00 ` Alex Williamson
2022-05-11 6:40 ` Leon Romanovsky [this message]
2022-05-12 18:21 ` Alex Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YntaZcd+Qv5UiQRN@unreal \
--to=leon@kernel$(echo .)org \
--cc=alex.williamson@redhat$(echo .)com \
--cc=cohuck@redhat$(echo .)com \
--cc=jgg@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=maorg@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=saeedm@nvidia$(echo .)com \
--cc=yishaih@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox