DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shiri Kuzin <shirik@mellanox.com>
To: dev@dpdk.org
Cc: matan@mellanox.com, rasland@mellanox.com, viacheslavo@mellanox.com
Subject: [dpdk-dev] [RFC 0/3] mlx5: LACP handling for bonded devices
Date: Tue,  2 Jun 2020 12:38:08 +0300	[thread overview]
Message-ID: <cover.1591088325.git.shirik@mellanox.com> (raw)

When the driver has a bond configured LACP traffic should
be steered to kernel to manage the bond using a new rdma-core
API.
This is done by creating a new internal action and adding a 
new devarg that will allow the user to manage the bond and 
get lacp traffic if they wish.  

Shiri Kuzin (3):
  common/mlx5: add default miss action
  net/mlx5: add default miss action to flow engine
  net/mlx5: add new devarg dv_lacp_by_user

 drivers/common/mlx5/Makefile    |  5 +++
 drivers/common/mlx5/meson.build |  2 +
 drivers/common/mlx5/mlx5_glue.c | 13 ++++++
 drivers/common/mlx5/mlx5_glue.h |  1 +
 drivers/net/mlx5/mlx5.c         |  6 +++
 drivers/net/mlx5/mlx5.h         |  7 ++++
 drivers/net/mlx5/mlx5_flow.c    | 72 ++++++++++++++++++++++++++++++++
 drivers/net/mlx5/mlx5_flow.h    | 10 ++++-
 drivers/net/mlx5/mlx5_flow_dv.c | 91 ++++++++++++++++++++++++++++++++++++++++-
 drivers/net/mlx5/mlx5_trigger.c |  9 ++++
 10 files changed, 213 insertions(+), 3 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2020-06-02  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02  9:38 Shiri Kuzin [this message]
2020-06-02  9:38 ` [dpdk-dev] [RFC 1/3] common/mlx5: add default miss action Shiri Kuzin
2020-06-02  9:38 ` [dpdk-dev] [RFC 2/3] net/mlx5: add default miss action to flow engine Shiri Kuzin
2020-06-02  9:38 ` [dpdk-dev] [RFC 3/3] net/mlx5: add new devarg dv_lacp_by_user Shiri Kuzin

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=cover.1591088325.git.shirik@mellanox.com \
    --to=shirik@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=viacheslavo@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).