DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 0/2] net/mlx5: fix flow rules for external SQ
Date: Sun, 12 Nov 2023 14:27:28 +0000	[thread overview]
Message-ID: <MN0PR12MB6056DE0CDFA0DA18AFA8A5F2CFACA@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231109085547.1313003-1-suanmingm@nvidia.com>

Hi,

> -----Original Message-----
> From: Suanming Mou <suanmingm@nvidia.com>
> Sent: Thursday, November 9, 2023 10:56 AM
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH 0/2] net/mlx5: fix flow rules for external SQ
> 
> If representor matching was enabled (device argument repr_matching_en is
> equal to 1, default configuration), then during registration of external SQs,
> mlx5 PMD would not create control flow rules in NIC Tx domain. This caused
> an issue with packet metadata. If a packet sent on external SQ had packet
> metadata attached, then it would be lost when it would go from NIC Tx to FDB
> domain.
> 
> Meanwhile, the external SQ flow rules should be managed individually and not
> be destroyed internally by PMD.
> 
> This series fixes these two issues for the external SQ flow rules in
> rte_pmd_mlx5_external_sq_enable().
> 
> Dariusz Sosnowski (1):
>   net/mlx5: fix missing flow rules for external SQ
> 
> Suanming Mou (1):
>   net/mlx5: fix destroying external representor matched flows
> 
>  drivers/net/mlx5/mlx5.h         |  41 ++++++++++
>  drivers/net/mlx5/mlx5_flow.h    |   6 +-
>  drivers/net/mlx5/mlx5_flow_hw.c | 132
> ++++++++++++++++++++++++++++----
>  drivers/net/mlx5/mlx5_trigger.c |   4 +-
>  drivers/net/mlx5/mlx5_txq.c     |  12 ++-
>  5 files changed, 176 insertions(+), 19 deletions(-)
> 
> --
> 2.34.1

Fixed a typo in the first commit, and fixed a warning for a line too long
Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2023-11-12 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09  8:55 Suanming Mou
2023-11-09  8:55 ` [PATCH 1/2] net/mlx5: fix missing " Suanming Mou
2023-11-09  8:55 ` [PATCH 2/2] net/mlx5: fix destroying external representor matched flows Suanming Mou
2023-11-12 14:27 ` 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=MN0PR12MB6056DE0CDFA0DA18AFA8A5F2CFACA@MN0PR12MB6056.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=suanmingm@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).