From: Rongwei Liu <rongweil@nvidia.com>
To: <matan@nvidia.com>, <viacheslavo@nvidia.com>, <orika@nvidia.com>,
<thomas@monjalon.net>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [dpdk-dev] [PATCH v2 0/2] support socket direct mode bonding
Date: Tue, 28 Sep 2021 11:50:52 +0300 [thread overview]
Message-ID: <20210928085054.1619915-1-rongweil@nvidia.com> (raw)
In socket direct mode, it's possible to bind any two (maybe four
in the future) PCIe devices with IDs like xxxx:xx:xx.x and
yyyy:yy:yy.y. Bonding member interfaces are unnecessary to have
the same PCIe domain/bus/device ID anymore.
Doesn't need to backport to DPDK 20.11
v2: fix ci warnings.
Rongwei Liu (2):
common/mlx5: support pcie device guid query
net/mlx5: support socket direct mode bonding
drivers/common/mlx5/linux/mlx5_common_os.c | 41 +++++++++++++++++++++
drivers/common/mlx5/linux/mlx5_common_os.h | 19 ++++++++++
drivers/net/mlx5/linux/mlx5_os.c | 43 +++++++++++++++++-----
3 files changed, 94 insertions(+), 9 deletions(-)
--
2.27.0
next reply other threads:[~2021-09-28 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 8:50 Rongwei Liu [this message]
2021-09-28 8:50 ` [dpdk-dev] [PATCH v2 1/2] common/mlx5: support pcie device guid query Rongwei Liu
2021-09-28 8:50 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: support socket direct mode bonding Rongwei Liu
2021-09-29 21:58 ` Thomas Monjalon
2021-10-04 6:45 ` Slava Ovsiienko
2021-10-08 10:05 ` [dpdk-dev] [PATCH v3 0/2] " Rongwei Liu
2021-10-08 10:05 ` [dpdk-dev] [PATCH v3 1/2] common/mlx5: support pcie device guid query Rongwei Liu
2021-10-08 10:05 ` [dpdk-dev] [PATCH v3 2/2] net/mlx5: support socket direct mode bonding Rongwei Liu
2021-10-14 2:57 ` [dpdk-dev] [PATCH v4 0/2] " Rongwei Liu
2021-10-14 2:58 ` [dpdk-dev] [PATCH v4 1/2] common/mlx5: support pcie device guid query Rongwei Liu
2021-10-14 2:58 ` [dpdk-dev] [PATCH v4 2/2] net/mlx5: support socket direct mode bonding Rongwei Liu
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=20210928085054.1619915-1-rongweil@nvidia.com \
--to=rongweil@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--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).