From: Steve Lin <steven.lin1@broadcom.com>
To: netdev@vger.kernel.org
Cc: jiri@mellanox.com, davem@davemloft.net,
michael.chan@broadcom.com, linville@tuxdriver.com,
gospo@broadcom.com, yuvalm@mellanox.com,
steven.lin1@broadcom.com
Subject: [PATCH net-next v4 09/10] bnxt: Adding max PF MSI-X vectors perm config param
Date: Fri, 27 Oct 2017 16:54:13 -0400 [thread overview]
Message-ID: <1509137654-1580-10-git-send-email-steven.lin1@broadcom.com> (raw)
In-Reply-To: <1509137654-1580-1-git-send-email-steven.lin1@broadcom.com>
Adding permanent config parameter for maximum number of PF
MSI-X vectors.
Signed-off-by: Steve Lin <steven.lin1@broadcom.com>
Acked-by: Andy Gospodarek <gospo@broadcom.com>
---
drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c b/drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c
index 0812221..047f09e 100644
--- a/drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c
+++ b/drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c
@@ -20,12 +20,16 @@
* DEVLINK_PERM_CONFIG_ENABLE = enable SR-IOV
* DEVLINK_PERM_CONFIG_NUM_VF_PER_PF:
* # of VFs per PF in SR-IOV mode
+ * DEVLINK_PERM_CONFIG_MAX_NUM_PF_MSIX_VECT:
+ * Max # of MSI-X vectors per PF
*/
struct bnxt_drv_cfgparam bnxt_drv_cfgparam_list[] = {
{DEVLINK_PERM_CONFIG_SRIOV_ENABLED, BNXT_DRV_PF,
BNXT_DRV_APPL_SHARED, 1, 401},
{DEVLINK_PERM_CONFIG_NUM_VF_PER_PF, BNXT_DRV_PF,
BNXT_DRV_APPL_FUNCTION, 8, 404},
+ {DEVLINK_PERM_CONFIG_NUM_PF_MSIX_VECT, BNXT_DRV_PF,
+ BNXT_DRV_APPL_SHARED, 10, 108},
};
#define BNXT_NUM_DRV_CFGPARAM ARRAY_SIZE(bnxt_drv_cfgparam_list)
--
2.7.4
next prev parent reply other threads:[~2017-10-27 20:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 20:54 [PATCH net-next v4 00/10] Adding permanent config get/set to devlink Steve Lin
2017-10-27 20:54 ` [PATCH net-next v4 01/10] devlink: Add permanent config parameter get/set operations Steve Lin
2017-10-27 21:04 ` Jiri Pirko
2017-10-27 21:26 ` Steve Lin
2017-10-28 7:16 ` Jiri Pirko
2017-10-27 20:54 ` [PATCH net-next v4 02/10] devlink: Adding SR-IOV enablement perm config param Steve Lin
2017-10-27 21:06 ` Jiri Pirko
2017-10-27 21:30 ` Steve Lin
2017-10-28 7:17 ` Jiri Pirko
2017-10-27 20:54 ` [PATCH net-next v4 03/10] devlink: Adding num VFs per PF permanent " Steve Lin
2017-10-27 20:54 ` [PATCH net-next v4 04/10] devlink: Adding max PF MSI-X vectors perm " Steve Lin
2017-10-27 20:54 ` [PATCH net-next v4 05/10] devlink: Adding num MSI-X vectors per VF " Steve Lin
2017-10-27 20:54 ` [PATCH net-next v4 06/10] bnxt: Add devlink support for config get/set Steve Lin
2017-10-27 20:54 ` [PATCH net-next v4 07/10] bnxt: Adding SR-IOV enablement permanent cfg param Steve Lin
2017-10-27 20:54 ` [PATCH net-next v4 08/10] bnxt: Adding num VFs per PF perm config param Steve Lin
2017-10-27 20:54 ` Steve Lin [this message]
2017-10-27 20:54 ` [PATCH net-next v4 10/10] bnxt: Adding num MSI-X vectors per VF " Steve Lin
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=1509137654-1580-10-git-send-email-steven.lin1@broadcom.com \
--to=steven.lin1@broadcom.com \
--cc=davem@davemloft.net \
--cc=gospo@broadcom.com \
--cc=jiri@mellanox.com \
--cc=linville@tuxdriver.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=yuvalm@mellanox.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).