DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1405] Static Memory footprint large increase due to net/bnxt changes in 23.11
Date: Wed, 20 Mar 2024 19:07:50 +0000	[thread overview]
Message-ID: <bug-1405-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1405

            Bug ID: 1405
           Summary: Static Memory footprint large increase due to net/bnxt
                    changes in 23.11
           Product: DPDK
           Version: 23.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: nicolas.chautru@intel.com
  Target Milestone: ---

The memory footprint has increased massively when the commit "97435d7906
net/bnxt: update Truflow core" was added.
The bss in my example going from 6M to 94M when building any dpdk-test
applicationfor instance, when that commit is introduced. 
There are now notably huge memory reserved for cfa_tcam_mgr_* from the bnxt PMD
visible from nm.

That issue is notably impacting v23.11 and still seen on main as of today. 

For now for application building with 23.11, we recommend to disable the
net/bnxt through meson to avoid this issue.

I believe a proper fix is required from Broadcom bnxt: --cc Ajit Khaparde
<ajit.khaparde@broadcom.com>, Somnath Kotur <somnath.kotur@broadcom.com>, Randy
Schacher <stuart.schacher@broadcom.com>


Nic

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3422 bytes --]

                 reply	other threads:[~2024-03-20 19:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1405-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).