From: Raslan Darawsheh <rasland@mellanox.com>
To: Vu Pham <vuhuong@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@mellanox.com>,
Ori Kam <orika@mellanox.com>, Matan Azrad <matan@mellanox.com>,
Vu Pham <vuhuong@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v4 0/2] refactor multi-process IPC and memory management codes to common driver
Date: Wed, 15 Apr 2020 09:30:11 +0000 [thread overview]
Message-ID: <AM0PR05MB6707818F2EF4CD19E6BF3B6AC2DB0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200413211748.20500-1-vuhuong@mellanox.com>
Hi,
> -----Original Message-----
> From: Vu Pham <vuhuong@mellanox.com>
> Sent: Tuesday, April 14, 2020 12:18 AM
> To: dev@dpdk.org
> Cc: Slava Ovsiienko <viacheslavo@mellanox.com>; Ori Kam
> <orika@mellanox.com>; Matan Azrad <matan@mellanox.com>; Raslan
> Darawsheh <rasland@mellanox.com>; Vu Pham <vuhuong@mellanox.com>
> Subject: [PATCH v4 0/2] refactor multi-process IPC and memory
> management codes to common driver
>
> Current mlx5 net PMD and future mlx5(regex,...) PMDs that run
> and share the same HCAs need to use common memory management
> driver. Memory management codes embeddedly use multi-process IPC
> for primary/secondary processes to register and sync on memory
> registrations MRs. That's the main reason to refactor and move
> multi-process IPC APIs to mlx5 common driver and make it become
> the base commit, then refactor and move common MR codes to
> common driver in subsequent patch.
>
> Vu Pham (2):
> common/mlx5: refactor multi-process IPC handling codes to common
> driver
> common/mlx5: refactor memory management codes
>
> drivers/common/mlx5/Makefile | 4 +-
> drivers/common/mlx5/meson.build | 2 +
> drivers/common/mlx5/mlx5_common_mp.c | 188 ++++
> drivers/common/mlx5/mlx5_common_mp.h | 98 ++
> drivers/common/mlx5/mlx5_common_mr.c | 1108
> +++++++++++++++++++++
> drivers/common/mlx5/mlx5_common_mr.h | 160 ++++
> drivers/common/mlx5/rte_common_mlx5_version.map | 27 +
> drivers/net/mlx5/mlx5.c | 19 +-
> drivers/net/mlx5/mlx5.h | 55 +-
> drivers/net/mlx5/mlx5_mp.c | 242 +----
> drivers/net/mlx5/mlx5_mr.c | 1169 +----------------------
> drivers/net/mlx5/mlx5_mr.h | 87 +-
> drivers/net/mlx5/mlx5_rxtx.c | 4 +-
> drivers/net/mlx5/mlx5_rxtx.h | 10 +-
> drivers/net/mlx5/mlx5_rxtx_vec.h | 2 +
> drivers/net/mlx5/mlx5_trigger.c | 1 +
> drivers/net/mlx5/mlx5_txq.c | 3 +-
> 17 files changed, 1692 insertions(+), 1487 deletions(-)
> create mode 100644 drivers/common/mlx5/mlx5_common_mp.c
> create mode 100644 drivers/common/mlx5/mlx5_common_mp.h
> create mode 100644 drivers/common/mlx5/mlx5_common_mr.c
> create mode 100644 drivers/common/mlx5/mlx5_common_mr.h
>
> --
> 2.16.6
Fixed first commit title too long,
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-04-15 9:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 19:21 [dpdk-dev] [PATCH 0/4] " Vu Pham
2020-04-02 19:21 ` [dpdk-dev] [PATCH 1/4] common/mlx5: refactor multi-process IPC handling " Vu Pham
2020-04-02 19:21 ` [dpdk-dev] [PATCH 2/4] net/mlx5: modify net PMD to use common multi-process APIs Vu Pham
2020-04-02 19:21 ` [dpdk-dev] [PATCH 3/4] common/mlx5: refactor memory management codes Vu Pham
2020-04-02 19:21 ` [dpdk-dev] [PATCH 4/4] net/mlx5: modify net PMD to use common memory management driver Vu Pham
2020-04-07 16:48 ` [dpdk-dev] [PATCH v2 0/4] refactor multi-process IPC and memory management codes to common driver Vu Pham
2020-04-07 16:48 ` [dpdk-dev] [PATCH v2 1/4] common/mlx5: refactor MP IPC handling " Vu Pham
2020-04-08 9:05 ` Slava Ovsiienko
2020-04-07 16:48 ` [dpdk-dev] [PATCH v2 2/4] net/mlx5: modify net pmd to use common multi-process APIs Vu Pham
2020-04-07 16:48 ` [dpdk-dev] [PATCH v2 3/4] common/mlx5: refactor memory management codes Vu Pham
2020-04-07 16:48 ` [dpdk-dev] [PATCH v2 4/4] net/mlx5: modify net pmd to use common MR driver Vu Pham
2020-04-07 17:00 ` [dpdk-dev] [PATCH v3 0/4] refactor multi-process IPC and memory management codes to common driver Vu Pham
2020-04-07 17:00 ` [dpdk-dev] [PATCH v3 1/4] common/mlx5: refactor multi-process IPC handling " Vu Pham
2020-04-08 9:05 ` Slava Ovsiienko
2020-04-07 17:00 ` [dpdk-dev] [PATCH v3 2/4] net/mlx5: modify net PMD to use common multi-process APIs Vu Pham
2020-04-08 9:05 ` Slava Ovsiienko
2020-04-07 17:00 ` [dpdk-dev] [PATCH v3 3/4] common/mlx5: refactor memory management codes Vu Pham
2020-04-08 9:04 ` Slava Ovsiienko
2020-04-07 17:00 ` [dpdk-dev] [PATCH v3 4/4] net/mlx5: modify net PMD to use common MR driver Vu Pham
2020-04-08 9:06 ` Slava Ovsiienko
2020-04-13 21:17 ` [dpdk-dev] [PATCH v4 0/2] refactor multi-process IPC and memory management codes to common driver Vu Pham
2020-04-13 21:17 ` [dpdk-dev] [PATCH v4 1/2] common/mlx5: refactor multi-process IPC handling " Vu Pham
2020-04-14 7:26 ` Slava Ovsiienko
2020-04-13 21:17 ` [dpdk-dev] [PATCH v4 2/2] common/mlx5: refactor memory management codes Vu Pham
2020-04-14 7:27 ` Slava Ovsiienko
2020-04-15 9:30 ` 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=AM0PR05MB6707818F2EF4CD19E6BF3B6AC2DB0@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=orika@mellanox.com \
--cc=viacheslavo@mellanox.com \
--cc=vuhuong@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).