netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, steven.lin1@broadcom.com
Subject: [PATCH net-next v2 5/6] devlink: Adding num MSI-X vectors per VF NVRAM config param
Date: Thu, 19 Oct 2017 15:17:09 -0400	[thread overview]
Message-ID: <1508440630-25830-6-git-send-email-steven.lin1@broadcom.com> (raw)
In-Reply-To: <1508440630-25830-1-git-send-email-steven.lin1@broadcom.com>

Adding DEVLINK_PERM_CONFIG_MSIX_VECTORS_PER_VF permanent config
parameter.  Defines number of MSI-X vectors allocated per VF.
Value is permanent (stored in NVRAM), so becomes the new default
value for this device.

Signed-off-by: Steve Lin <steven.lin1@broadcom.com>
Acked-by: Andy Gospodarek <gospo@broadcom.com>
---
 include/uapi/linux/devlink.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/uapi/linux/devlink.h b/include/uapi/linux/devlink.h
index 8ad6c63..ef163b6 100644
--- a/include/uapi/linux/devlink.h
+++ b/include/uapi/linux/devlink.h
@@ -260,6 +260,7 @@ enum devlink_perm_config_param {
 	DEVLINK_PERM_CONFIG_SRIOV_ENABLED,
 	DEVLINK_PERM_CONFIG_NUM_VF_PER_PF,
 	DEVLINK_PERM_CONFIG_MAX_NUM_PF_MSIX_VECT,
+	DEVLINK_PERM_CONFIG_MSIX_VECTORS_PER_VF,
 };
 
 #endif /* _UAPI_LINUX_DEVLINK_H_ */
-- 
2.7.4

  parent reply	other threads:[~2017-10-19 19:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 19:17 [PATCH net-next v2 0/6] Adding permanent config get/set to devlink Steve Lin
2017-10-19 19:17 ` [PATCH net-next v2 1/6] devlink: Add permanent config parameter get/set operations Steve Lin
2017-10-19 20:21   ` Yuval Mintz
2017-10-20 13:11     ` Steve Lin
2017-10-21 14:12       ` Yuval Mintz
2017-10-23 15:27         ` Steve Lin
2017-10-20 14:39   ` Jiri Pirko
2017-10-20 15:13     ` Steve Lin
2017-10-21  9:24       ` Jiri Pirko
2017-10-23 14:05         ` Steve Lin
2017-10-19 19:17 ` [PATCH net-next v2 2/6] devlink: Adding SR-IOV enablement NVRAM config param Steve Lin
2017-10-19 19:33   ` Jiri Pirko
2017-10-19 20:40     ` Steve Lin
2017-10-19 19:17 ` [PATCH net-next v2 3/6] devlink: Adding num VFs per PF " Steve Lin
2017-10-19 19:17 ` [PATCH net-next v2 4/6] devlink: Adding max PF MSI-X vectors " Steve Lin
2017-10-19 19:17 ` Steve Lin [this message]
2017-10-19 20:32   ` [PATCH net-next v2 5/6] devlink: Adding num MSI-X vectors per VF " Yuval Mintz
2017-10-19 21:39     ` Jiri Pirko
2017-10-19 21:43       ` Jiri Pirko
2017-10-20  1:01         ` Florian Fainelli
2017-10-20  6:44           ` Jiri Pirko
2017-10-20 14:03       ` Steve Lin
2017-10-20 14:10         ` Jiri Pirko
2017-10-20 14:19           ` Steve Lin
2017-10-21 13:59             ` Yuval Mintz
2017-10-23 14:20               ` Steve Lin
2017-10-23 14:37                 ` Yuval Mintz
2017-10-23 16:35                   ` Steve Lin
2017-10-23 18:41                     ` Yuval Mintz
2017-10-19 19:17 ` [PATCH net-next v2 6/6] bnxt: Add devlink support for config get/set Steve Lin
2017-10-19 19:35   ` Jiri Pirko
2017-10-19 20:40     ` 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=1508440630-25830-6-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 \
    /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).