From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
To: dev@dpdk.org
Cc: shahafs@mellanox.com
Subject: [dpdk-dev] [PATCH 0/4] support DR/DV flows over shared IB context
Date: Tue, 2 Apr 2019 06:22:33 +0000 [thread overview]
Message-ID: <1554186157-29455-1-git-send-email-viacheslavo@mellanox.com> (raw)
Message-ID: <20190402062233._I-QTqRouoCpOYzV0CPj7DROIJf2x_vcvv14DC_z5rs@z> (raw)
The Direct Rules/Direct Verbs flows support is going
to be added [1]. The master/representor over multiport
IB device is added [2]. This patchset adds support for
DR/DV flows with shared IB context over multiport IB
device.
The DV/DR flows applied to the master/representors on the
same IB device share the following entinies:
- rx/tx namespaces
- rx/tx flow tables
- matchers
- encap/decap action resources
- flow tags (MARK actions)
- modify action resources
- jump tables
[1] "net/mlx5: Add Direct Rule support"
http://patches.dpdk.org/cover/51856/
[2] "net/mlx5: add support for multiport IB devices"
http://patches.dpdk.org/cover/51800/
Viacheslav Ovsiienko (4):
net/mlx5: add DV/DR flow data alloc/free routines
net/mlx5: add reference counter for DV/DR structures
net/mlx5: share DV/DR flow related structures
net/mlx5: add mutex for shared DV/DR structures
drivers/net/mlx5/mlx5.c | 118 ++++++++++++++++++++++++++----
drivers/net/mlx5/mlx5.h | 45 ++++++------
drivers/net/mlx5/mlx5_flow_dv.c | 155 +++++++++++++++++++++++++++++++++-------
3 files changed, 258 insertions(+), 60 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-04-02 6:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 6:22 Viacheslav Ovsiienko [this message]
2019-04-02 6:22 ` Viacheslav Ovsiienko
2019-04-02 6:22 ` [dpdk-dev] [PATCH 1/4] net/mlx5: add DV/DR flow data alloc/free routines Viacheslav Ovsiienko
2019-04-02 6:22 ` Viacheslav Ovsiienko
2019-04-02 19:09 ` Shahaf Shuler
2019-04-02 19:09 ` Shahaf Shuler
2019-04-02 6:22 ` [dpdk-dev] [PATCH 2/4] net/mlx5: add reference counter for DV/DR structures Viacheslav Ovsiienko
2019-04-02 6:22 ` Viacheslav Ovsiienko
2019-04-02 19:09 ` Shahaf Shuler
2019-04-02 19:09 ` Shahaf Shuler
2019-04-03 13:27 ` Slava Ovsiienko
2019-04-03 13:27 ` Slava Ovsiienko
2019-04-02 6:22 ` [dpdk-dev] [PATCH 3/4] net/mlx5: share DV/DR flow related structures Viacheslav Ovsiienko
2019-04-02 6:22 ` Viacheslav Ovsiienko
2019-04-02 19:09 ` Shahaf Shuler
2019-04-02 19:09 ` Shahaf Shuler
2019-04-02 6:22 ` [dpdk-dev] [PATCH 4/4] net/mlx5: add mutex for shared DV/DR structures Viacheslav Ovsiienko
2019-04-02 6:22 ` Viacheslav Ovsiienko
2019-04-02 19:09 ` Shahaf Shuler
2019-04-02 19:09 ` Shahaf Shuler
2019-04-04 13:04 ` [dpdk-dev] [PATCH v2 0/2] support Direct Rules flows over shared IB context Viacheslav Ovsiienko
2019-04-04 13:04 ` Viacheslav Ovsiienko
2019-04-04 13:04 ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: add Direct Rules flow data alloc/free routines Viacheslav Ovsiienko
2019-04-04 13:04 ` Viacheslav Ovsiienko
2019-04-04 13:04 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: share Direct Rules/Verbs flow related structures Viacheslav Ovsiienko
2019-04-04 13:04 ` Viacheslav Ovsiienko
2019-04-04 18:57 ` [dpdk-dev] [PATCH v2 0/2] support Direct Rules flows over shared IB context Shahaf Shuler
2019-04-04 18:57 ` 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=1554186157-29455-1-git-send-email-viacheslavo@mellanox.com \
--to=viacheslavo@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).