DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v1 00/18] mlx5 Rx DevX/Verbs separation
Date: Tue, 8 Sep 2020 11:46:32 +0000	[thread overview]
Message-ID: <DM6PR12MB2748773DBE75DDCE816330A2CF290@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1599128029-2092-1-git-send-email-michaelba@nvidia.com>

Hi,

> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Thursday, September 3, 2020 1:14 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH v1 00/18] mlx5 Rx DevX/Verbs separation
> 
> v1:
> Initial version
> 
> Michael Baum (18):
>   net/mlx5: fix Rx hash queue creation error flow
>   net/mlx5: fix Rx queue state update
>   net/mlx5: fix types differentiation in Rxq create
>   net/mlx5: mitigate Rx queue reference counters
>   net/mlx5: separate Rx queue object creations
>   net/mlx5: separate Rx interrupt handling
>   net/mlx5: share Rx control code
>   net/mlx5: rearrange the creation of RQ and CQ resources
>   net/mlx5: rearrange the creation of WQ and CQ object
>   net/mlx5: separate Rx queue object modification
>   net/mlx5: share Rx queue object modification
>   net/mlx5: separate Rx indirection table object creation
>   net/mlx5: separate Rx hash queue creation
>   net/mlx5: remove indirection table type field
>   net/mlx5: share Rx queue indirection table code
>   net/mlx5: share Rx hash queue code
>   net/mlx5: separate Rx queue drop
>   net/mlx5: share Rx queue drop action code
> 
>  drivers/net/mlx5/Makefile           |    1 +
>  drivers/net/mlx5/linux/mlx5_os.c    |   10 +
>  drivers/net/mlx5/linux/mlx5_verbs.c |  707 +++++++++++++
>  drivers/net/mlx5/linux/mlx5_verbs.h |    4 +
>  drivers/net/mlx5/meson.build        |    1 +
>  drivers/net/mlx5/mlx5.h             |   73 +-
>  drivers/net/mlx5/mlx5_devx.c        |  792 +++++++++++++-
>  drivers/net/mlx5/mlx5_flow_dv.c     |   20 +-
>  drivers/net/mlx5/mlx5_flow_verbs.c  |   35 +-
>  drivers/net/mlx5/mlx5_rxq.c         | 1934 ++++++-----------------------------
>  drivers/net/mlx5/mlx5_rxtx.h        |   84 +-
>  drivers/net/mlx5/mlx5_trigger.c     |   67 +-
>  drivers/net/mlx5/mlx5_vlan.c        |    2 +-
>  13 files changed, 1954 insertions(+), 1776 deletions(-)
> 
> --
> 1.8.3.1

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2020-09-08 11:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 10:13 Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 01/18] net/mlx5: fix Rx hash queue creation error flow Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 02/18] net/mlx5: fix Rx queue state update Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 03/18] net/mlx5: fix types differentiation in Rxq create Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 04/18] net/mlx5: mitigate Rx queue reference counters Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 05/18] net/mlx5: separate Rx queue object creations Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 06/18] net/mlx5: separate Rx interrupt handling Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 07/18] net/mlx5: share Rx control code Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 08/18] net/mlx5: rearrange the creation of RQ and CQ resources Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 09/18] net/mlx5: rearrange the creation of WQ and CQ object Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 10/18] net/mlx5: separate Rx queue object modification Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 11/18] net/mlx5: share " Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 12/18] net/mlx5: separate Rx indirection table object creation Michael Baum
2020-09-09 11:29   ` Ferruh Yigit
2020-09-09 14:37     ` Matan Azrad
2020-09-09 16:28       ` Ferruh Yigit
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 13/18] net/mlx5: separate Rx hash queue creation Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 14/18] net/mlx5: remove indirection table type field Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 15/18] net/mlx5: share Rx queue indirection table code Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 16/18] net/mlx5: share Rx hash queue code Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 17/18] net/mlx5: separate Rx queue drop Michael Baum
2020-09-03 10:13 ` [dpdk-dev] [PATCH v1 18/18] net/mlx5: share Rx queue drop action code Michael Baum
2020-09-03 14:34 ` [dpdk-dev] [PATCH v1 00/18] mlx5 Rx DevX/Verbs separation Tom Barbette
2020-09-03 20:59   ` Michael Baum
2020-09-04  7:30     ` David Marchand
2020-09-04  7:47     ` Thomas Monjalon
2020-09-06  7:32       ` Michael Baum
2020-09-08 11:46 ` 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=DM6PR12MB2748773DBE75DDCE816330A2CF290@DM6PR12MB2748.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=michaelba@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).