From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
To: shahafs@mellanox.com
Cc: dev@dpdk.org, yskoh@mellanox.com
Subject: [dpdk-dev] [PATCH v3 0/2] net/mlx5: share Memory Regions for multiport devices
Date: Sat, 27 Apr 2019 04:32:55 +0000 [thread overview]
Message-ID: <1556339577-18185-1-git-send-email-viacheslavo@mellanox.com> (raw)
Message-ID: <20190427043255.QjJ_WIcKDc01X6GHwkp2mw9phSKAOcshNjTfJPZmlks@z> (raw)
In-Reply-To: <1556095470-11407-1-git-send-email-viacheslavo@mellanox.com>
The patches [1] and [2] are both related to Memory Regions sharing and their
applying order matters, this series just combines ones.
The multiport Infiniband device support was introduced [3].
All active ports, belonging to the same Infiniband device use the single
shared Infiniband context of that device and share the resources:
- QPs are created within shared context
- Verbs flows are also created with specifying port index
- DV/DR resources
- Protection Domain
- Event Handlers
This patchset adds support for Memory Regions sharing between
ports, created on the base of multiport Infiniband device.
The datapath of mlx5 uses the layered cache subsystem for
allocating/releasing Memory Regions, only the lowest layer L3
is subject to share due to performance issues.
[1] http://patches.dpdk.org/patch/53040/
[2] http://patches.dpdk.org/patch/53041/
[3] http://patches.dpdk.org/cover/51800/
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
---
v3:
- combine two patches in pathset
- commit messages spellcheck
v2:
- intendation issues
- comments cleanup
v1:
http://patches.dpdk.org/patch/52723/
Viacheslav Ovsiienko (2):
net/mlx5: share Memory Regions for multiport device
net/mlx5: update memory event callback for shared context
drivers/net/mlx5/mlx5.c | 42 +++++---
drivers/net/mlx5/mlx5.h | 21 ++--
drivers/net/mlx5/mlx5_mr.c | 245 ++++++++++++++++++++++----------------------
drivers/net/mlx5/mlx5_mr.h | 5 +-
drivers/net/mlx5/mlx5_txq.c | 2 +-
5 files changed, 162 insertions(+), 153 deletions(-)
--
1.8.3.1
next prev parent reply other threads:[~2019-04-27 4:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 15:45 [dpdk-dev] [PATCH 1/1] net/mlx5: share Memory Regions for multiport device Viacheslav Ovsiienko
2019-04-12 15:45 ` Viacheslav Ovsiienko
2019-04-12 19:22 ` Yongseok Koh
2019-04-12 19:22 ` Yongseok Koh
2019-04-15 6:42 ` Slava Ovsiienko
2019-04-15 6:42 ` Slava Ovsiienko
2019-04-24 8:44 ` [dpdk-dev] [PATCH v2] " Viacheslav Ovsiienko
2019-04-24 8:44 ` Viacheslav Ovsiienko
2019-04-24 8:52 ` Yongseok Koh
2019-04-24 8:52 ` Yongseok Koh
2019-04-27 4:32 ` Viacheslav Ovsiienko [this message]
2019-04-27 4:32 ` [dpdk-dev] [PATCH v3 0/2] net/mlx5: share Memory Regions for multiport devices Viacheslav Ovsiienko
2019-04-27 4:32 ` [dpdk-dev] [PATCH v3 1/2] net/mlx5: share Memory Regions for multiport device Viacheslav Ovsiienko
2019-04-27 4:32 ` Viacheslav Ovsiienko
2019-04-27 4:32 ` [dpdk-dev] [PATCH v3 2/2] net/mlx5: update memory event callback for shared context Viacheslav Ovsiienko
2019-04-27 4:32 ` Viacheslav Ovsiienko
2019-04-29 8:54 ` [dpdk-dev] [PATCH v3 0/2] net/mlx5: share Memory Regions for multiport devices Shahaf Shuler
2019-04-29 8:54 ` Shahaf Shuler
2019-04-24 8:48 ` [dpdk-dev] [PATCH] net/mlx5: update memory event callback for shared context Viacheslav Ovsiienko
2019-04-24 8:48 ` Viacheslav Ovsiienko
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=1556339577-18185-1-git-send-email-viacheslavo@mellanox.com \
--to=viacheslavo@mellanox.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=yskoh@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).