All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Yishai Hadas <yishaih@nvidia.com>, alex.williamson@redhat.com
Cc: 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: Tue, 10 May 2022 16:16:16 +0300	[thread overview]
Message-ID: <YnploMZRI9jXMXAi@unreal> (raw)
In-Reply-To: <20220510090206.90374-1-yishaih@nvidia.com>

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

Thanks

  parent reply	other threads:[~2022-05-10 13:20 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 ` Leon Romanovsky [this message]
2022-05-10 15:00   ` [PATCH V2 mlx5-next 0/4] Improve mlx5 live migration driver Alex Williamson
2022-05-11  6:40     ` Leon Romanovsky
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=YnploMZRI9jXMXAi@unreal \
    --to=leon@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=maorg@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=yishaih@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.