From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1 0/9] bug fixes for bnxt PMD
Date: Sat, 16 May 2020 08:12:13 -0700 [thread overview]
Message-ID: <CACZ4nhsEpxTYugYgN0TDgrtqcRFBnd=eo3XLy1eV90doJ8P-Tg@mail.gmail.com> (raw)
In-Reply-To: <20200515184542.89318-1-ajit.khaparde@broadcom.com>
On Fri, May 15, 2020 at 11:45 AM Ajit Khaparde <ajit.khaparde@broadcom.com>
wrote:
> Patchset with fixes.
> The patch [1/9] enhances the log message in case of a FW command
> timeout. The rest of the patches address a perf regression.
> Recent commits caused a regression in performance because
> bnxt structure became too big and noticed in rc2.
> Most of the patches reduce the memory footprint of the struct bnxt.
> With these changes the performance is back to normal.
>
> Ajit Khaparde (7):
> net/bnxt: fix error log for command timeout
> net/bnxt: fix to alloc LED config info
> net/bnxt: fix to alloc COS queue info dynamically
> net/bnxt: fix to allocate flow stat related structs
> net/bnxt: fix to alloc link info struct
> net/bnxt: fix to alloc PF info structure
> net/bnxt: fix to use RSS config from eth dev struct
>
> Kalesh AP (1):
> net/bnxt: fix to remove unneeded structure variable
>
> Mike Baucom (1):
> net/bnxt: fix to allocate bnxt ulp context
>
> drivers/net/bnxt/bnxt.h | 47 ++--
> drivers/net/bnxt/bnxt_cpr.c | 20 +-
> drivers/net/bnxt/bnxt_ethdev.c | 331 ++++++++++++++++++++---------
> drivers/net/bnxt/bnxt_filter.c | 12 +-
> drivers/net/bnxt/bnxt_flow.c | 14 +-
> drivers/net/bnxt/bnxt_hwrm.c | 205 +++++++++---------
> drivers/net/bnxt/bnxt_rxq.c | 4 +-
> drivers/net/bnxt/bnxt_rxr.c | 4 +-
> drivers/net/bnxt/bnxt_stats.c | 14 +-
> drivers/net/bnxt/rte_pmd_bnxt.c | 98 ++++-----
> drivers/net/bnxt/tf_ulp/bnxt_ulp.c | 64 ++++--
> 11 files changed, 492 insertions(+), 321 deletions(-)
>
Patchset applied to dpdk-next-net-brcm. Thanks
prev parent reply other threads:[~2020-05-16 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 18:45 Ajit Khaparde
2020-05-15 18:45 ` [dpdk-dev] [PATCH v1 1/9] net/bnxt: fix error log for command timeout Ajit Khaparde
2020-05-15 18:45 ` [dpdk-dev] [PATCH v1 2/9] net/bnxt: fix to alloc LED config info Ajit Khaparde
2020-05-15 18:45 ` [dpdk-dev] [PATCH v1 3/9] net/bnxt: fix to alloc COS queue info dynamically Ajit Khaparde
2020-05-15 18:45 ` [dpdk-dev] [PATCH v1 4/9] net/bnxt: fix to allocate flow stat related structs Ajit Khaparde
2020-05-15 18:45 ` [dpdk-dev] [PATCH v1 5/9] net/bnxt: fix to alloc link info struct Ajit Khaparde
2020-05-15 18:45 ` [dpdk-dev] [PATCH v1 6/9] net/bnxt: fix to alloc PF info structure Ajit Khaparde
2020-05-15 18:45 ` [dpdk-dev] [PATCH v1 7/9] net/bnxt: fix to use RSS config from eth dev struct Ajit Khaparde
2020-05-15 18:45 ` [dpdk-dev] [PATCH v1 8/9] net/bnxt: fix to remove unneeded structure variable Ajit Khaparde
2020-05-15 18:45 ` [dpdk-dev] [PATCH v1 9/9] net/bnxt: fix to allocate bnxt ulp context Ajit Khaparde
2020-05-16 15:12 ` Ajit Khaparde [this message]
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='CACZ4nhsEpxTYugYgN0TDgrtqcRFBnd=eo3XLy1eV90doJ8P-Tg@mail.gmail.com' \
--to=ajit.khaparde@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).