From: Yongseok Koh <yskoh@mellanox.com>
To: shahafs@mellanox.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/3] net/mlx4: add secondary process support
Date: Mon, 25 Mar 2019 12:17:58 -0700 [thread overview]
Message-ID: <20190325191801.20841-1-yskoh@mellanox.com> (raw)
Message-ID: <20190325191758.kPweHH5Z9nwIHnha4KFzR9I2Hn4zWUnmd5bqPXQ06oc@z> (raw)
In-Reply-To: <20190307073905.18615-1-yskoh@mellanox.com>
RFC:
https://mails.dpdk.org/archives/dev/2019-March/125516.html
v2:
* add more sanity check for eth_dev and return value from IPC request.
* complement commit messages
* add MLX5_MP_REQ_TIMEOUT_SEC
Yongseok Koh (3):
net/mlx4: change device reference for secondary process
net/mlx4: add external allocator for Verbs object
net/mlx4: add secondary process support
doc/guides/nics/features/mlx4.ini | 1 +
doc/guides/nics/mlx4.rst | 10 +
drivers/net/mlx4/Makefile | 11 +
drivers/net/mlx4/meson.build | 13 ++
drivers/net/mlx4/mlx4.c | 449 ++++++++++++++++++++++++++++++++++++--
drivers/net/mlx4/mlx4.h | 85 +++++++-
drivers/net/mlx4/mlx4_flow.c | 39 ++--
drivers/net/mlx4/mlx4_intr.c | 20 +-
drivers/net/mlx4/mlx4_mp.c | 304 ++++++++++++++++++++++++++
drivers/net/mlx4/mlx4_mr.c | 40 +++-
drivers/net/mlx4/mlx4_prm.h | 4 +-
drivers/net/mlx4/mlx4_rxq.c | 40 ++--
drivers/net/mlx4/mlx4_rxtx.c | 2 +
drivers/net/mlx4/mlx4_rxtx.h | 1 +
drivers/net/mlx4/mlx4_txq.c | 125 ++++++++++-
15 files changed, 1064 insertions(+), 80 deletions(-)
create mode 100644 drivers/net/mlx4/mlx4_mp.c
--
2.11.0
next prev parent reply other threads:[~2019-03-25 19:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 7:39 [dpdk-dev] [PATCH " Yongseok Koh
2019-03-07 7:39 ` [dpdk-dev] [PATCH 1/3] net/mlx4: change device reference for secondary process Yongseok Koh
2019-03-07 7:39 ` [dpdk-dev] [PATCH 2/3] net/mlx4: add external allocator for Verbs object Yongseok Koh
2019-03-07 7:39 ` [dpdk-dev] [PATCH 3/3] net/mlx4: add secondary process support Yongseok Koh
2019-03-25 19:17 ` Yongseok Koh [this message]
2019-03-25 19:17 ` [dpdk-dev] [PATCH v2 0/3] " Yongseok Koh
2019-03-25 19:17 ` [dpdk-dev] [PATCH v2 1/3] net/mlx4: change device reference for secondary process Yongseok Koh
2019-03-25 19:17 ` Yongseok Koh
2019-03-26 19:16 ` Shahaf Shuler
2019-03-26 19:16 ` Shahaf Shuler
2019-03-25 19:18 ` [dpdk-dev] [PATCH v2 2/3] net/mlx4: add external allocator for Verbs object Yongseok Koh
2019-03-25 19:18 ` Yongseok Koh
2019-03-26 19:21 ` Shahaf Shuler
2019-03-26 19:21 ` Shahaf Shuler
2019-03-25 19:18 ` [dpdk-dev] [PATCH v2 3/3] net/mlx4: add secondary process support Yongseok Koh
2019-03-25 19:18 ` Yongseok Koh
2019-03-26 19:33 ` Shahaf Shuler
2019-03-26 19:33 ` Shahaf Shuler
2019-03-28 19:01 ` Yongseok Koh
2019-03-28 19:01 ` Yongseok Koh
2019-04-01 21:15 ` [dpdk-dev] [PATCH v3 0/3] " Yongseok Koh
2019-04-01 21:15 ` Yongseok Koh
2019-04-01 21:15 ` [dpdk-dev] [PATCH v3 1/3] net/mlx4: change device reference for secondary process Yongseok Koh
2019-04-01 21:15 ` Yongseok Koh
2019-04-01 21:15 ` [dpdk-dev] [PATCH v3 2/3] net/mlx4: add external allocator for Verbs object Yongseok Koh
2019-04-01 21:15 ` Yongseok Koh
2019-04-01 21:15 ` [dpdk-dev] [PATCH v3 3/3] net/mlx4: add secondary process support Yongseok Koh
2019-04-01 21:15 ` Yongseok Koh
2019-04-02 7:12 ` [dpdk-dev] [PATCH v3 0/3] " Shahaf Shuler
2019-04-02 7:12 ` Shahaf Shuler
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=20190325191801.20841-1-yskoh@mellanox.com \
--to=yskoh@mellanox.com \
--cc=dev@dpdk.org \
--cc=shahafs@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).