DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: "Jiawei(Jonny) Wang" <jiaweiw@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Ori Kam <orika@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2 0/3] Add Tx queue mapping of aggregated ports in MLX5 PMD
Date: Sun, 26 Feb 2023 14:35:37 +0000	[thread overview]
Message-ID: <BYAPR12MB30787AB2B7AF66AAD59B14B4CFAE9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230222122628.29627-1-jiaweiw@nvidia.com>

Hi,

> -----Original Message-----
> From: Jiawei(Jonny) Wang <jiaweiw@nvidia.com>
> Sent: Wednesday, February 22, 2023 2:26 PM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v2 0/3] Add Tx queue mapping of aggregated ports in MLX5
> PMD
> 
> This patch implements RTE_FLOW_ITEM_TYPE_AGGR_AFFINITY support in
> MLX5 PMD.
> 
> This patch adds the MLX5 PMD support for two device ops:
>  - map_aggr_tx_affinity
>  - count_aggr_ports
> 
> This patch series relies on the preceding RTE API:
> http://patches.dpdk.org/project/dpdk/list/?series=27064
> 
> v2:
>  * update the PMD code based on the new RTE API.
> 
> Jiawei Wang (3):
>   net/mlx5: add lag Rx port affinity in PRM
>   net/mlx5: add aggregated affinity item support
>   net/mlx5: enhance the Tx queue affinity
> 
>  doc/guides/nics/features/default.ini |   1 +
>  doc/guides/nics/features/mlx5.ini    |   1 +
>  doc/guides/nics/mlx5.rst             |   6 ++
>  drivers/common/mlx5/mlx5_devx_cmds.c |   3 +
>  drivers/common/mlx5/mlx5_devx_cmds.h |   1 +
>  drivers/common/mlx5/mlx5_prm.h       |  15 ++--
>  drivers/net/mlx5/linux/mlx5_os.c     |   6 ++
>  drivers/net/mlx5/mlx5.c              |  49 ++++++-------
>  drivers/net/mlx5/mlx5.h              |   3 +
>  drivers/net/mlx5/mlx5_devx.c         |  24 ++++---
>  drivers/net/mlx5/mlx5_flow.h         |   3 +
>  drivers/net/mlx5/mlx5_flow_dv.c      | 100
> ++++++++++++++++++++++++++-
>  drivers/net/mlx5/mlx5_flow_hw.c      |  14 ++++
>  drivers/net/mlx5/mlx5_tx.h           |   4 ++
>  drivers/net/mlx5/mlx5_txq.c          |  38 ++++++++++
>  15 files changed, 221 insertions(+), 47 deletions(-)
> 
> --
> 2.18.1

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2023-02-26 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03  5:21 [PATCH 0/3] add new PHY affinity support " Jiawei Wang
2023-02-03  5:21 ` [PATCH 1/3] drivers: add lag Rx port affinity in PRM Jiawei Wang
2023-02-03  5:21 ` [PATCH 2/3] net/mlx5: add PHY affinity item support Jiawei Wang
2023-02-03  5:21 ` [PATCH 3/3] drivers: enhance the Tx queue affinity Jiawei Wang
2023-02-22 12:26 ` [PATCH v2 0/3] Add Tx queue mapping of aggregated ports in MLX5 PMD Jiawei Wang
2023-02-22 12:26   ` [PATCH v2 1/3] net/mlx5: add lag Rx port affinity in PRM Jiawei Wang
2023-02-22 12:26   ` [PATCH v2 2/3] net/mlx5: add aggregated affinity item support Jiawei Wang
2023-02-22 12:26   ` [PATCH v2 3/3] net/mlx5: enhance the Tx queue affinity Jiawei Wang
2023-02-26 14:35   ` 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=BYAPR12MB30787AB2B7AF66AAD59B14B4CFAE9@BYAPR12MB3078.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=jiaweiw@nvidia.com \
    --cc=orika@nvidia.com \
    --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).