From: Ophir Munk <ophirmu@mellanox.com>
To: dev@dpdk.org, Matan Azrad <matan@mellanox.com>,
Raslan Darawsheh <rasland@mellanox.com>
Cc: Ophir Munk <ophirmu@mellanox.com>
Subject: [dpdk-dev] [PATCH v1 0/8] mlx5 PMD multi OS support - part #2
Date: Wed, 10 Jun 2020 09:32:25 +0000 [thread overview]
Message-ID: <20200610093233.23902-1-ophirmu@mellanox.com> (raw)
This patch series is part of preparing mlx5 PMD to compile and run under
multiple OSs. Part #2
v1:
Initial release
Ophir Munk (8):
net/mlx5: remove dv dependency in mlx5_dev_ctx_shared struct
net/mlx5: rename ib in names
net/mlx5: move socket files under Linux directory
net/mlx5: split mlx5 ethdev under Linux directory
net/mlx5: refactor eth dev ops for Linux
common/mlx5: exclude ibv dependent calls in devx commands
common/mlx5: exclude OS dependency in devx commands
net/mlx5: refactor statistics
drivers/common/mlx5/linux/mlx5_common_os.c | 12 +
drivers/common/mlx5/mlx5_common.h | 1 +
drivers/common/mlx5/mlx5_devx_cmds.c | 9 +-
drivers/net/mlx5/Makefile | 3 +-
drivers/net/mlx5/linux/meson.build | 2 +
drivers/net/mlx5/linux/mlx5_ethdev_os.c | 1270 ++++++++++++++++++++++++++++
drivers/net/mlx5/linux/mlx5_os.c | 481 ++++++++++-
drivers/net/mlx5/linux/mlx5_socket.c | 230 +++++
drivers/net/mlx5/meson.build | 1 -
drivers/net/mlx5/mlx5.c | 172 +---
drivers/net/mlx5/mlx5.h | 55 +-
drivers/net/mlx5/mlx5_ethdev.c | 1257 +--------------------------
drivers/net/mlx5/mlx5_flow.c | 10 +-
drivers/net/mlx5/mlx5_flow_dv.c | 4 +-
drivers/net/mlx5/mlx5_flow_verbs.c | 2 +-
drivers/net/mlx5/mlx5_rxtx.c | 2 +-
drivers/net/mlx5/mlx5_socket.c | 230 -----
drivers/net/mlx5/mlx5_stats.c | 332 +-------
drivers/net/mlx5/mlx5_trigger.c | 10 +-
drivers/net/mlx5/mlx5_txq.c | 2 +-
20 files changed, 2081 insertions(+), 2004 deletions(-)
create mode 100644 drivers/net/mlx5/linux/mlx5_ethdev_os.c
create mode 100644 drivers/net/mlx5/linux/mlx5_socket.c
delete mode 100644 drivers/net/mlx5/mlx5_socket.c
--
2.8.4
next reply other threads:[~2020-06-10 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 9:32 Ophir Munk [this message]
2020-06-10 9:32 ` [dpdk-dev] [PATCH v1 1/8] net/mlx5: remove dv dependency in mlx5_dev_ctx_shared struct Ophir Munk
2020-06-10 9:32 ` [dpdk-dev] [PATCH v1 2/8] net/mlx5: rename ib in names Ophir Munk
2020-06-10 9:32 ` [dpdk-dev] [PATCH v1 3/8] net/mlx5: move socket files under Linux directory Ophir Munk
2020-06-10 9:32 ` [dpdk-dev] [PATCH v1 4/8] net/mlx5: split mlx5 ethdev " Ophir Munk
2020-06-10 9:32 ` [dpdk-dev] [PATCH v1 5/8] net/mlx5: refactor eth dev ops for Linux Ophir Munk
2020-06-10 9:32 ` [dpdk-dev] [PATCH v1 6/8] common/mlx5: exclude ibv dependent calls in devx commands Ophir Munk
2020-06-10 9:32 ` [dpdk-dev] [PATCH v1 7/8] common/mlx5: exclude OS dependency " Ophir Munk
2020-06-18 22:47 ` Thomas Monjalon
2020-06-18 22:48 ` Thomas Monjalon
2020-06-10 9:32 ` [dpdk-dev] [PATCH v1 8/8] net/mlx5: refactor statistics Ophir Munk
2020-06-14 8:21 ` [dpdk-dev] [PATCH v1 0/8] mlx5 PMD multi OS support - part #2 Matan Azrad
2020-06-15 6:58 ` Raslan Darawsheh
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=20200610093233.23902-1-ophirmu@mellanox.com \
--to=ophirmu@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=rasland@mellanox.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).