DPDK patches and discussions
 help / color / mirror / Atom feed
From: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
To: dev@dpdk.org
Cc: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Subject: [dpdk-dev] [PATCH 0/5] introduce changes to support flow scaling
Date: Sat, 25 Apr 2020 09:17:21 +0530	[thread overview]
Message-ID: <1587786446-35230-1-git-send-email-venkatkumar.duvvuru@broadcom.com> (raw)

This patchset introduces changes to the action record allocation, flow
database entry deletion, and hw flow cache updates.  Action record
allocation now allows the actions to scale with the flows.
Additionally, resources attached to a flow database entry are now
correctly released when the critical resource has not been added to
the flow.  Finally, the hw flow cache has a timer to periodically
invalidate flow entries.

Farah Smith (1):
  net/bnxt: action record external pool updates

Mike Baucom (3):
  net/bnxt: reserve a flowdb resource function as invalid
  net/bnxt: ulp modifications for handling actions/index tables
  net/bnxt: ulp must set hw flow cache timer when allocating table scope

Shahaji Bhosle (1):
  net/bnxt: add truflow flush-timer to alloc table scope API

 drivers/net/bnxt/tf_core/tf_core.c        |   3 -
 drivers/net/bnxt/tf_core/tf_core.h        |  21 +++--
 drivers/net/bnxt/tf_core/tf_msg.c         |   3 +
 drivers/net/bnxt/tf_core/tf_msg.h         |   1 +
 drivers/net/bnxt/tf_core/tf_rm.c          |   3 -
 drivers/net/bnxt/tf_core/tf_session.h     |   6 --
 drivers/net/bnxt/tf_core/tf_tbl.c         | 137 ++++++++++++------------------
 drivers/net/bnxt/tf_core/tf_tbl.h         |   4 +-
 drivers/net/bnxt/tf_ulp/bnxt_ulp.c        |   6 ++
 drivers/net/bnxt/tf_ulp/ulp_mapper.c      |  30 ++++---
 drivers/net/bnxt/tf_ulp/ulp_template_db.h |  15 ++--
 11 files changed, 106 insertions(+), 123 deletions(-)

-- 
2.7.4


             reply	other threads:[~2020-04-25  3:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25  3:47 Venkat Duvvuru [this message]
2020-04-25  3:47 ` [dpdk-dev] [PATCH 1/5] net/bnxt: reserve a flowdb resource function as invalid Venkat Duvvuru
2020-04-25  3:47 ` [dpdk-dev] [PATCH 2/5] net/bnxt: action record external pool updates Venkat Duvvuru
2020-04-25  3:47 ` [dpdk-dev] [PATCH 3/5] net/bnxt: ulp modifications for handling actions/index tables Venkat Duvvuru
2020-04-25  3:47 ` [dpdk-dev] [PATCH 4/5] net/bnxt: add truflow flush-timer to alloc table scope API Venkat Duvvuru
2020-04-25  3:47 ` [dpdk-dev] [PATCH 5/5] net/bnxt: ulp must set hw flow cache timer when allocating table scope Venkat Duvvuru
2020-04-25 14:01 ` [dpdk-dev] [PATCH v2 0/4] introduce changes to support flow scaling Ajit Khaparde
2020-04-25 14:01   ` [dpdk-dev] [PATCH v2 1/4] net/bnxt: reserve a flowdb resource function as invalid Ajit Khaparde
2020-04-25 14:01   ` [dpdk-dev] [PATCH v2 2/4] net/bnxt: update action record external pool Ajit Khaparde
2020-04-25 14:01   ` [dpdk-dev] [PATCH v2 3/4] net/bnxt: ulp changes to handle action/index tables Ajit Khaparde
2020-04-25 14:01   ` [dpdk-dev] [PATCH v2 4/4] net/bnxt: add truflow flush-timer to alloc table scope API Ajit Khaparde
2020-04-25 17:36   ` [dpdk-dev] [PATCH v2 0/4] introduce changes to support flow scaling Ajit Khaparde

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=1587786446-35230-1-git-send-email-venkatkumar.duvvuru@broadcom.com \
    --to=venkatkumar.duvvuru@broadcom.com \
    --cc=dev@dpdk.org \
    /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).