patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Bing Zhao <bingz@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>, Ori Kam <orika@nvidia.com>,
	NBU-Contact-N?lio Laranjeiro <nelio.laranjeiro@6wind.com>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix the RETA update without stopping device
Date: Wed, 10 Nov 2021 08:48:15 +0000	[thread overview]
Message-ID: <DM4PR12MB53127DDA122D7BB243AB742DCF939@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211105061057.121797-1-bingz@nvidia.com>

Hi,

> -----Original Message-----
> From: Bing Zhao <bingz@nvidia.com>
> Sent: Friday, November 5, 2021 8:11 AM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>;
> stable@dpdk.org; Ori Kam <orika@nvidia.com>; NBU-Contact-N?lio
> Laranjeiro <nelio.laranjeiro@6wind.com>
> Subject: [PATCH] net/mlx5: fix the RETA update without stopping device
> 
> The global redirection table is used to create the default flow
> rules for the ingress traffic with the lowest priority. It is also
> used to create the default RSS rule in the destination table when
> there is a tunnel offload.
> 
> To update the RETA in-flight, there is no restriction in the ethdev
> API. In the previous implementation of mlx5, a port restart was
> needed to make the new configuration take effect.
> 
> The restart is heavy, e.g., all the queues will be released and
> reallocated, users' rules will be flushed. Since the restart is
> internal, there is a risk to crash the application when some change
> in the ethdev is introduced but no workaround is done in mlx5 PMD.
> 
> The users' rules, including the default miss rule for tunnul
> offload, should not be impacted by the RETA update. It is improper
> to flush all rules when updating RETA.
> 
> With this patch, only the default rules will be flushed and
> re-created with the new table configuration.
> 
> Fixes: 3f2fe392bd49 ("net/mlx5: fix crash during RETA update")
> Cc: nelio.laranjeiro@6wind.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Bing Zhao <bingz@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2021-11-10  8:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  6:10 Bing Zhao
2021-11-10  8:48 ` 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=DM4PR12MB53127DDA122D7BB243AB742DCF939@DM4PR12MB5312.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=orika@nvidia.com \
    --cc=stable@dpdk.org \
    --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).