From: Jiri Pirko <jiri@resnulli.us>
To: Geetha sowjanya <gakula@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, sgoutham@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com
Subject: Re: [PATCH v2 0/2] Dynamically allocate BPIDs for LBK
Date: Wed, 31 Jan 2024 10:52:17 +0100 [thread overview]
Message-ID: <ZboYUXiT2H40mWrL@nanopsycho> (raw)
In-Reply-To: <20240131075441.17227-1-gakula@marvell.com>
Wed, Jan 31, 2024 at 08:54:39AM CET, gakula@marvell.com wrote:
>In current driver 64 BPIDs are reserved for LBK interfaces.
>These bpids are 1-to-1 mapped to LBK interface channel numbers.
>In some usecases one LBK interface required more than one bpids
>and in some case they may not require at all. These usescas
>can't be address with the current implementation as it always
>reserves only one bpid per LBK channel.
>
>This patch addresses this issue by creating free bpid pool from
>these 64 bpids instead of 1-to-1 mapping to the lbk channel.
>Now based on usecase LBK interface can request a bpid using (bp_enable()).
>
>
>v1 -> v2:
> - Modified commit message.
> - Dropped patch2, as for now rvu netdev have no usecase. Will
> be upstream along with the CPT driver.
> - Addressed review comments by Simon Horman.
>
>Geetha sowjanya (2):
> octeontx2-af: Create BPIDs free pool
> octeontx2-af: Cleanup loopback device checks
>
> .../net/ethernet/marvell/octeontx2/af/mbox.h | 2 +
> .../net/ethernet/marvell/octeontx2/af/rvu.c | 14 +-
> .../net/ethernet/marvell/octeontx2/af/rvu.h | 21 +-
> .../ethernet/marvell/octeontx2/af/rvu_nix.c | 179 ++++++++++++++----
> .../ethernet/marvell/octeontx2/af/rvu_npc.c | 8 +-
> .../ethernet/marvell/octeontx2/af/rvu_reg.h | 3 +
> .../ethernet/marvell/octeontx2/af/rvu_sdp.c | 6 +-
> 7 files changed, 181 insertions(+), 52 deletions(-)
FWIW: I don't see anything problematic in this patchset. From that
perspective:
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2024-01-31 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 7:54 [PATCH v2 0/2] Dynamically allocate BPIDs for LBK Geetha sowjanya
2024-01-31 7:54 ` [net-next v2 PATCH 1/2] octeontx2-af: Create BPIDs free pool Geetha sowjanya
2024-01-31 7:54 ` [net-next v2 PATCH 2/2] octeontx2-af: Cleanup loopback device checks Geetha sowjanya
2024-01-31 9:52 ` Jiri Pirko [this message]
2024-02-02 12:20 ` [PATCH v2 0/2] Dynamically allocate BPIDs for LBK patchwork-bot+netdevbpf
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=ZboYUXiT2H40mWrL@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).