From: Jakub Kicinski <kuba@kernel.org>
To: Geetha sowjanya <gakula@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<davem@davemloft.net>, <pabeni@redhat.com>, <edumazet@google.com>,
<sgoutham@marvell.com>, <sbhatta@marvell.com>,
<hkelam@marvell.com>
Subject: Re: [net-next PATCH 0/3] Dynamically allocate BPIDs
Date: Thu, 25 Jan 2024 18:16:46 -0800 [thread overview]
Message-ID: <20240125181646.522e6d35@kernel.org> (raw)
In-Reply-To: <20240124055014.32694-1-gakula@marvell.com>
On Wed, 24 Jan 2024 11:20:11 +0530 Geetha sowjanya wrote:
> Current hw support 512 backpressure(BP) Ids. These BPIDs are
> statically reserved among 4 interface types based on number
> of channels supported. Latest HW support configuring
> multiple BPIDs per channel. To support this feature, the
> patch set creates BPIDs free pool from the BPIDs reserved for
> LBK channel as, LBK uses single BPIDs across multiple channels
> and on request it dynamically allocates N number of bpids
> from the free pool. This patch also reworks the LBK device id
> checks.
I looked at this for 20 min, I don't understand how this fits together.
Please improve the commit messages to also explain the functionality
and how user interacts with the features.
next prev parent reply other threads:[~2024-01-26 2:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 5:50 [net-next PATCH 0/3] Dynamically allocate BPIDs Geetha sowjanya
2024-01-24 5:50 ` [net-next PATCH 1/3] octeontx2-af: Create BPIDs free pool Geetha sowjanya
2024-01-25 11:33 ` Simon Horman
2024-01-26 9:52 ` [EXT] " Geethasowjanya Akula
2024-01-24 5:50 ` [net-next PATCH 2/3] octeontx2-af: Add mbox to alloc/free BPIDs Geetha sowjanya
2024-01-25 11:33 ` Simon Horman
2024-01-24 5:50 ` [net-next PATCH 3/3] octeontx2-af: Cleanup loopback device checks Geetha sowjanya
2024-01-25 11:34 ` Simon Horman
2024-01-26 2:16 ` Jakub Kicinski [this message]
2024-01-26 9:54 ` [EXT] Re: [net-next PATCH 0/3] Dynamically allocate BPIDs Geethasowjanya Akula
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=20240125181646.522e6d35@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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