From: Simon Horman <horms@kernel.org>
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, pavan.chebbi@broadcom.com,
andrew.gospodarek@broadcom.com,
Hongguang Gao <hongguang.gao@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>
Subject: Re: [PATCH net-next 8/9] bnxt_en: Allocate the max bp->irq_tbl size for dynamic msix allocation
Date: Mon, 15 Jul 2024 10:30:42 +0100 [thread overview]
Message-ID: <20240715093042.GK8432@kernel.org> (raw)
In-Reply-To: <20240713234339.70293-9-michael.chan@broadcom.com>
On Sat, Jul 13, 2024 at 04:43:38PM -0700, Michael Chan wrote:
> If dynamic MSIX allocation is supported, additional MSIX can be
> allocated at run-time without reinitializing the existing MSIX entries.
> The first step to support this dynamic scheme is to alloacte a large
> enough bp->irq_tbl if dynamic allocation is supported.
>
> Reviewed-by: Hongguang Gao <hongguang.gao@broadcom.com>
> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
> Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-07-15 9:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 23:43 [PATCH net-next 0/9] bnxt_en: Update for net-next Michael Chan
2024-07-13 23:43 ` [PATCH net-next 1/9] bnxt_en: add support for storing crash dump into host memory Michael Chan
2024-07-15 9:28 ` Simon Horman
2024-07-13 23:43 ` [PATCH net-next 2/9] bnxt_en: add support for retrieving crash dump using ethtool Michael Chan
2024-07-15 9:28 ` Simon Horman
2024-07-13 23:43 ` [PATCH net-next 3/9] bnxt_en: Support QOS and TPID settings for the SRIOV VLAN Michael Chan
2024-07-15 9:17 ` Simon Horman
2024-07-13 23:43 ` [PATCH net-next 4/9] bnxt_en: Deprecate support for legacy INTX mode Michael Chan
2024-07-15 9:28 ` Simon Horman
2024-07-15 16:24 ` Michael Chan
2024-07-16 16:57 ` Dan Carpenter
2024-07-16 17:28 ` Michael Chan
2024-07-13 23:43 ` [PATCH net-next 5/9] bnxt_en: Remove BNXT_FLAG_USING_MSIX flag Michael Chan
2024-07-15 9:29 ` Simon Horman
2024-07-15 17:32 ` Bjorn Helgaas
2024-07-15 18:00 ` Michael Chan
2024-07-13 23:43 ` [PATCH net-next 6/9] bnxt_en: Remove register mapping to support INTX Michael Chan
2024-07-15 9:30 ` Simon Horman
2024-07-15 17:27 ` Bjorn Helgaas
2024-07-13 23:43 ` [PATCH net-next 7/9] bnxt_en: Replace deprecated PCI MSIX APIs Michael Chan
2024-07-15 9:30 ` Simon Horman
2024-07-13 23:43 ` [PATCH net-next 8/9] bnxt_en: Allocate the max bp->irq_tbl size for dynamic msix allocation Michael Chan
2024-07-15 9:30 ` Simon Horman [this message]
2024-07-15 17:33 ` Bjorn Helgaas
2024-07-13 23:43 ` [PATCH net-next 9/9] bnxt_en: Support dynamic MSIX Michael Chan
2024-07-15 9:31 ` Simon Horman
2024-07-15 17:34 ` Bjorn Helgaas
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=20240715093042.GK8432@kernel.org \
--to=horms@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hongguang.gao@broadcom.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=somnath.kotur@broadcom.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).