From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Priyanshu Singh <singhpriyanshu9838@gmail.com>
Cc: "Dan Carpenter" <error27@gmail.com>,
"Oscar Alejandro Sánchez Lucero" <aleszlucero@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: octeon: fix asymmetric output buffer pool accounting
Date: Mon, 16 Nov 2026 10:40:46 +0100 [thread overview]
Message-ID: <2026111624-amendment-bulge-7a08@gregkh> (raw)
In-Reply-To: <20261116065730.472784-1-singhpriyanshu9838@gmail.com>
On Mon, Nov 16, 2026 at 06:57:30AM +0000, Priyanshu Singh wrote:
> In cvm_oct_configure_common_hw(), when CVMX_FPA_OUTPUT_BUFFER_POOL differs
> from CVMX_FPA_PACKET_POOL, 1024 output buffers are allocated and added to
> the hardware Free Pool Allocator (FPA) pool. However, in cvm_oct_probe()
> (err_tx:) and in cvm_oct_remove(), cvm_oct_mem_empty_fpa() is called with
> 128 instead of 1024 as the expected buffer count.
>
> This asymmetric accounting causes cvm_oct_free_hw_memory() to report a
> false warning ("Freeing of pool 2 had too many buffers (-896)") upon
> draining the pool.
>
> Define CVM_OCT_NUM_OUTPUT_BUFFERS in ethernet-defines.h and use this
> constant across cvm_oct_configure_common_hw(),
> cvm_oct_probe(), and cvm_oct_remove() to ensure symmetric allocation
> and deallocation.
>
> This was found via manual code inspection and is compile-tested only.
Please test this on real hardware in order for us to be able to accept
it.
thanks,
greg k-h
next prev parent reply other threads:[~2026-11-16 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 6:57 [PATCH v3] staging: octeon: fix asymmetric output buffer pool accounting Priyanshu Singh
2026-11-16 9:40 ` Greg Kroah-Hartman [this message]
2026-11-16 10:16 ` ASH
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=2026111624-amendment-bulge-7a08@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aleszlucero@gmail.com \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=singhpriyanshu9838@gmail.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