From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: dev@dpdk.org
Cc: shaguna@chelsio.com, indranil@chelsio.com, nirranjan@chelsio.com
Subject: [dpdk-dev] [PATCH 0/4] net/cxgbe: add destination MAC match and VLAN rewrite support for flow API
Date: Mon, 27 Aug 2018 18:22:28 +0530 [thread overview]
Message-ID: <cover.1535292771.git.rahul.lakkireddy@chelsio.com> (raw)
This series of patches add support to offload flows with destination MAC
match item and VLAN push/pop/rewrite actions.
Patch 1 adds API to program and manage hardware Layer 2 Table (L2T).
L2T holds destination node information to be used for VLAN rewrite.
Patch 2 implements offloading VLAN push/pop/rewrite actions.
Patch 3 adds API to program and manage hardware Multi Port Switch (MPS)
table. MPS holds the destination MAC addresses to be matched against
incoming packets.
Patch 4 implements offloading destination MAC match item.
Thanks,
Rahul
Shagun Agrawal (4):
net/cxgbe: add API to program hardware layer 2 table
net/cxgbe: add flow operations to offload vlan actions
net/cxgbe: add API to program hardware MPS table
net/cxgbe: add flow operations to match based on destination MAC
address
doc/guides/rel_notes/release_18_11.rst | 7 +
drivers/net/cxgbe/Makefile | 2 +
drivers/net/cxgbe/base/adapter.h | 4 +
drivers/net/cxgbe/base/common.h | 7 +
drivers/net/cxgbe/base/t4_hw.c | 108 ++++++++++++++
drivers/net/cxgbe/base/t4_msg.h | 40 ++++++
drivers/net/cxgbe/base/t4_regs.h | 8 ++
drivers/net/cxgbe/base/t4_tcb.h | 5 +
drivers/net/cxgbe/base/t4fw_interface.h | 26 ++++
drivers/net/cxgbe/cxgbe_ethdev.c | 4 +-
drivers/net/cxgbe/cxgbe_filter.c | 71 +++++++++-
drivers/net/cxgbe/cxgbe_filter.h | 11 ++
drivers/net/cxgbe/cxgbe_flow.c | 90 +++++++++++-
drivers/net/cxgbe/cxgbe_flow.h | 1 +
drivers/net/cxgbe/cxgbe_main.c | 43 ++++--
drivers/net/cxgbe/l2t.c | 227 +++++++++++++++++++++++++++++
drivers/net/cxgbe/l2t.h | 57 ++++++++
drivers/net/cxgbe/meson.build | 2 +
drivers/net/cxgbe/mps_tcam.c | 243 ++++++++++++++++++++++++++++++++
drivers/net/cxgbe/mps_tcam.h | 52 +++++++
20 files changed, 987 insertions(+), 21 deletions(-)
create mode 100644 drivers/net/cxgbe/l2t.c
create mode 100644 drivers/net/cxgbe/l2t.h
create mode 100644 drivers/net/cxgbe/mps_tcam.c
create mode 100644 drivers/net/cxgbe/mps_tcam.h
--
2.14.1
next reply other threads:[~2018-08-27 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 12:52 Rahul Lakkireddy [this message]
2018-08-27 12:52 ` [dpdk-dev] [PATCH 1/4] net/cxgbe: add API to program hardware layer 2 table Rahul Lakkireddy
2018-08-27 12:52 ` [dpdk-dev] [PATCH 2/4] net/cxgbe: add flow operations to offload vlan actions Rahul Lakkireddy
2018-08-27 12:52 ` [dpdk-dev] [PATCH 3/4] net/cxgbe: add API to program hardware MPS table Rahul Lakkireddy
2018-08-27 12:52 ` [dpdk-dev] [PATCH 4/4] net/cxgbe: add flow operations to match based on destination MAC address Rahul Lakkireddy
2018-09-13 14:03 ` [dpdk-dev] [PATCH 0/4] net/cxgbe: add destination MAC match and VLAN rewrite support for flow API Ferruh Yigit
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.1535292771.git.rahul.lakkireddy@chelsio.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=dev@dpdk.org \
--cc=indranil@chelsio.com \
--cc=nirranjan@chelsio.com \
--cc=shaguna@chelsio.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).