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 v2 0/6] net/mlx5: reduce Tx datapath compile time
Date: Thu, 15 Apr 2021 06:27:09 +0000
Message-ID: <DM6PR12MB27489527A6316A1CAB70486CCF4D9@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1618209145-3055-1-git-send-email-michaelba@nvidia.com>

Hi,

> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Monday, April 12, 2021 9:32 AM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH v2 0/6] net/mlx5: reduce Tx datapath compile time
> 
> The mlx5_rxtx.c file contains a lot of Tx burst functions, each of those is
> performance-optimized for the specific set of requested offloads.
> These ones are generated on the basis of the template function and it takes
> significant time to compile, just due to a large number of giant functions
> generated in the same file and this compilation is not being done in parallel
> with using multithreading.
> 
> Therefore, in this series we split the mlx5_rxtx.c file into several separate
> files to allow different functions to be compiled simultaneously.
> 
> v2: fix compilation error + rebase
> 
> Michael Baum (6):
>   net/mlx5: separate Rx function declarations to another file
>   net/mlx5: separate Rx function implementations to new file
>   net/mlx5: separate Tx function declarations to another file
>   net/mlx5: separate Tx burst template to header file
>   net/mlx5: separate Tx function implementations to new file
>   net/mlx5: separate Tx burst functions to different files
> 
>  drivers/net/mlx5/linux/mlx5_mp_os.c |    2 +
>  drivers/net/mlx5/linux/mlx5_os.c    |    2 +
>  drivers/net/mlx5/linux/mlx5_verbs.c |    3 +-
>  drivers/net/mlx5/meson.build        |    6 +
>  drivers/net/mlx5/mlx5.c             |    2 +
>  drivers/net/mlx5/mlx5_devx.c        |    3 +-
>  drivers/net/mlx5/mlx5_ethdev.c      |    2 +
>  drivers/net/mlx5/mlx5_flow.c        |    3 +-
>  drivers/net/mlx5/mlx5_flow_dv.c     |    3 +-
>  drivers/net/mlx5/mlx5_flow_verbs.c  |    2 +-
>  drivers/net/mlx5/mlx5_mr.c          |    2 +
>  drivers/net/mlx5/mlx5_rss.c         |    1 +
>  drivers/net/mlx5/mlx5_rx.c          | 1203 ++++++++
>  drivers/net/mlx5/mlx5_rx.h          |  598 ++++
>  drivers/net/mlx5/mlx5_rxmode.c      |    1 -
>  drivers/net/mlx5/mlx5_rxq.c         |    3 +-
>  drivers/net/mlx5/mlx5_rxtx.c        | 5468 +----------------------------------
>  drivers/net/mlx5/mlx5_rxtx.h        |  915 +-----
>  drivers/net/mlx5/mlx5_rxtx_vec.c    |    1 +
>  drivers/net/mlx5/mlx5_stats.c       |    3 +-
>  drivers/net/mlx5/mlx5_trigger.c     |    3 +-
>  drivers/net/mlx5/mlx5_tx.c          |  780 +++++
>  drivers/net/mlx5/mlx5_tx.h          | 3734 ++++++++++++++++++++++++
>  drivers/net/mlx5/mlx5_tx_empw.c     |   71 +
>  drivers/net/mlx5/mlx5_tx_mpw.c      |   34 +
>  drivers/net/mlx5/mlx5_tx_nompw.c    |   71 +
>  drivers/net/mlx5/mlx5_tx_txpp.c     |   45 +
>  drivers/net/mlx5/mlx5_txpp.c        |    3 +-
>  drivers/net/mlx5/mlx5_txq.c         |    2 +
>  drivers/net/mlx5/mlx5_vlan.c        |    1 +
>  drivers/net/mlx5/windows/mlx5_os.c  |    2 +
>  31 files changed, 6581 insertions(+), 6388 deletions(-)
>  create mode 100644 drivers/net/mlx5/mlx5_rx.c
>  create mode 100644 drivers/net/mlx5/mlx5_rx.h
>  create mode 100644 drivers/net/mlx5/mlx5_tx.c
>  create mode 100644 drivers/net/mlx5/mlx5_tx.h
>  create mode 100644 drivers/net/mlx5/mlx5_tx_empw.c
>  create mode 100644 drivers/net/mlx5/mlx5_tx_mpw.c
>  create mode 100644 drivers/net/mlx5/mlx5_tx_nompw.c
>  create mode 100644 drivers/net/mlx5/mlx5_tx_txpp.c
> 
> --
> 1.8.3.1

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2021-04-15  6:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 14:00 [dpdk-dev] [PATCH " Michael Baum
2021-04-05 14:00 ` [dpdk-dev] [PATCH 1/6] net/mlx5: separate Rx function declarations to another file Michael Baum
2021-04-06  9:27   ` Slava Ovsiienko
2021-04-05 14:00 ` [dpdk-dev] [PATCH 2/6] net/mlx5: separate Rx function implementations to new file Michael Baum
2021-04-06  9:27   ` Slava Ovsiienko
2021-04-05 14:00 ` [dpdk-dev] [PATCH 3/6] net/mlx5: separate Tx function declarations to another file Michael Baum
2021-04-06  9:28   ` Slava Ovsiienko
2021-04-07 11:33   ` Raslan Darawsheh
2021-04-05 14:00 ` [dpdk-dev] [PATCH 4/6] net/mlx5: separate Tx burst template to header file Michael Baum
2021-04-06  9:28   ` Slava Ovsiienko
2021-04-05 14:00 ` [dpdk-dev] [PATCH 5/6] net/mlx5: separate Tx function implementations to new file Michael Baum
2021-04-06  9:29   ` Slava Ovsiienko
2021-04-05 14:00 ` [dpdk-dev] [PATCH 6/6] net/mlx5: separate Tx burst functions to different files Michael Baum
2021-04-06  9:30   ` Slava Ovsiienko
2021-04-06  9:33 ` [dpdk-dev] [PATCH 0/6] net/mlx5: reduce Tx datapath compile time David Marchand
2021-04-06  9:58   ` Slava Ovsiienko
2021-04-12  6:32 ` [dpdk-dev] [PATCH v2 " Michael Baum
2021-04-12  6:32   ` [dpdk-dev] [PATCH v2 1/6] net/mlx5: separate Rx function declarations to another file Michael Baum
2021-04-12  6:32   ` [dpdk-dev] [PATCH v2 2/6] net/mlx5: separate Rx function implementations to new file Michael Baum
2021-04-16 13:08     ` Ferruh Yigit
2021-04-12  6:32   ` [dpdk-dev] [PATCH v2 3/6] net/mlx5: separate Tx function declarations to another file Michael Baum
2021-04-12  6:32   ` [dpdk-dev] [PATCH v2 4/6] net/mlx5: separate Tx burst template to header file Michael Baum
2021-04-12  6:32   ` [dpdk-dev] [PATCH v2 5/6] net/mlx5: separate Tx function implementations to new file Michael Baum
2021-04-12  6:32   ` [dpdk-dev] [PATCH v2 6/6] net/mlx5: separate Tx burst functions to different files Michael Baum
2021-04-15  6: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=DM6PR12MB27489527A6316A1CAB70486CCF4D9@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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git