From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] net/mlx5: share Memory Regions for multiport devices
Date: Mon, 29 Apr 2019 08:54:21 +0000 [thread overview]
Message-ID: <AM0PR0502MB3795E03AEF19DE62055E7C70C3390@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1556339577-18185-1-git-send-email-viacheslavo@mellanox.com>
Saturday, April 27, 2019 7:33 AM, Viacheslav Ovsiienko:
> Subject: [PATCH v3 0/2] net/mlx5: share Memory Regions for multiport
> devices
>
> 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>
Series applied to next-net-mlx, thanks.
next prev parent reply other threads:[~2019-04-29 8:54 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 ` [dpdk-dev] [PATCH v3 0/2] net/mlx5: share Memory Regions for multiport devices Viacheslav Ovsiienko
2019-04-27 4:32 ` 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 ` Shahaf Shuler [this message]
2019-04-29 8:54 ` [dpdk-dev] [PATCH v3 0/2] net/mlx5: share Memory Regions for multiport devices 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=AM0PR0502MB3795E03AEF19DE62055E7C70C3390@AM0PR0502MB3795.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=viacheslavo@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).