From: Somnath Kotur <somnath.kotur@broadcom.com>
To: dev <dev@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH 00/14] bnxt patches
Date: Fri, 17 Jul 2020 19:47:18 +0530 [thread overview]
Message-ID: <CAOBf=ms=Fj57y7ojaoz2nuYXvVZPOd0JDD5bQtVXzHFdMzkcng@mail.gmail.com> (raw)
In-Reply-To: <20200717141113.11613-1-somnath.kotur@broadcom.com>
On Fri, Jul 17, 2020 at 7:46 PM Somnath Kotur
<somnath.kotur@broadcom.com> wrote:
>
> From: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
>
> Some changes, cleanups/fixes in the TF-ULP layer
>
> Farah Smith (2):
> net/bnxt: initialize table scope rm parameters
> net/bnxt: fix em message size
>
> Jay Ding (1):
> net/bnxt: replace NAT IPv4 action SRC/DEST
>
> Kishore Padmanabha (6):
> net/bnxt: enable default flows in truflow mode
> net/bnxt: add protocol header info based on proto field data
> net/bnxt: fix dereference of a null pointer
> net/bnxt: default egress rule changes
> net/bnxt: update cfa truflow resource allocation numbers
> net/bnxt: enable support for exact match templates
>
> Peter Spreadborough (1):
> net/bnxt: changes to support new RM and multi-region
>
> Randy Schacher (2):
> net/bnxt: clean up em message definition
> net/bnxt: change header to SPDX-License
>
> Somnath Kotur (2):
> net/bnxt: fix to avoid accumulation of flow counters
> net/bnxt: remove unnecessary debug log
>
> drivers/net/bnxt/bnxt_ethdev.c | 5 +-
> drivers/net/bnxt/tf_core/cfa_resource_types.h | 207 +-
> drivers/net/bnxt/tf_core/tf_core.h | 16 +-
> drivers/net/bnxt/tf_core/tf_device_p4.h | 13 +-
> drivers/net/bnxt/tf_core/tf_em_common.c | 2 +-
> drivers/net/bnxt/tf_core/tf_msg.c | 3 +-
> drivers/net/bnxt/tf_core/tf_util.c | 18 +-
> drivers/net/bnxt/tf_ulp/bnxt_ulp.c | 35 +-
> drivers/net/bnxt/tf_ulp/bnxt_ulp.h | 9 +
> drivers/net/bnxt/tf_ulp/ulp_def_rules.c | 11 +-
> drivers/net/bnxt/tf_ulp/ulp_fc_mgr.c | 4 +-
> drivers/net/bnxt/tf_ulp/ulp_mapper.c | 3 -
> drivers/net/bnxt/tf_ulp/ulp_mark_mgr.c | 8 +-
> drivers/net/bnxt/tf_ulp/ulp_rte_parser.c | 180 +-
> drivers/net/bnxt/tf_ulp/ulp_template_db_act.c | 2547 +++-
> drivers/net/bnxt/tf_ulp/ulp_template_db_class.c | 17417 ++++++++++++++++++----
> drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h | 328 +-
> drivers/net/bnxt/tf_ulp/ulp_template_db_field.h | 959 +-
> drivers/net/bnxt/tf_ulp/ulp_template_db_tbl.c | 478 +-
> drivers/net/bnxt/tf_ulp/ulp_template_struct.h | 1 +
> 20 files changed, 18533 insertions(+), 3711 deletions(-)
>
> --
> 2.7.4
>
Please ignore, missed the 'reply-to'
next prev parent reply other threads:[~2020-07-17 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 14:10 Somnath Kotur
2020-07-17 14:11 ` [dpdk-dev] [PATCH 01/14] net/bnxt: changes to support new RM and multi-region Somnath Kotur
2020-07-17 14:11 ` [dpdk-dev] [PATCH 02/14] net/bnxt: initialize table scope rm parameters Somnath Kotur
2020-07-17 14:11 ` [dpdk-dev] [PATCH 03/14] net/bnxt: enable default flows in truflow mode Somnath Kotur
2020-07-17 14:17 ` Somnath Kotur [this message]
2020-07-17 14:28 ` [dpdk-dev] [PATCH 00/14] bnxt patches Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2020-10-17 6:27 Venkat Duvvuru
2020-07-17 9:49 Somnath Kotur
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='CAOBf=ms=Fj57y7ojaoz2nuYXvVZPOd0JDD5bQtVXzHFdMzkcng@mail.gmail.com' \
--to=somnath.kotur@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).