From: Raslan Darawsheh <rasland@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: RE: [PATCH v3] net/mlx5: support live migration
Date: Sun, 26 Feb 2023 11:09:05 +0000 [thread overview]
Message-ID: <BYAPR12MB3078B7995F08C584FBC6492ECFAE9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230215120345.3928888-1-rongweil@nvidia.com>
Hi,
> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Wednesday, February 15, 2023 2:04 PM
> To: dev@dpdk.org; Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-
> Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
> Cc: Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v3] net/mlx5: support live migration
>
> When a DPDK application must be upgraded, the traffic downtime should be
> shortened as much as possible.
> During the migration time, the old application may stay alive while the new
> application is starting and being configured.
>
> In order to optimize the switch to the new application, the old application
> may need to be aware of the presence of the new application being
> prepared.
> This is achieved with a new API allowing the user to change the new
> application state to standby and active later.
>
> The added function is trying to apply the new mode to all probed
> mlx5 ports. To make this API simple and easy to use, the same flags have to
> be accepted by all devices.
>
> This is the scenario of operations in the old and new applications:
> . device: already configured by the old application
> . new: start as active
> . new: probe the same device
> . new: set as standby
> . new: configure the device
> . device: has configurations from old and new applications
> . old: clear its device configuration
> . device: has only 1 configuration from new application
> . new: set as active
> . device: downtime for connecting all to the new application
> . old: shutdown
>
> The active mode means network handling configurations are programmed to
> the HW immediately, and no behavior changed. This is the default state.
> The standby mode means configurations are queued in the HW.
> If there is no application with active mode, any configuration is effective
> immediately.
>
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-02-26 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 12:03 Rongwei Liu
2023-02-26 11:09 ` Raslan Darawsheh [this message]
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=BYAPR12MB3078B7995F08C584FBC6492ECFAE9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).