From: Sathya Perla <sathya.perla@emulex.com>
To: <netdev@vger.kernel.org>
Cc: Vasundhara Volam <vasundhara.volam@emulex.com>,
Sathya Perla <sathya.perla@emulex.com>
Subject: [net-next PATCH 2/5] be2net: fix max VFs reported by HW
Date: Wed, 29 Aug 2012 12:07:41 +0530 [thread overview]
Message-ID: <3d88682f-40e6-48ec-b183-e768d4340c4b@exht1.ad.emulex.com> (raw)
In-Reply-To: <1346222264-20819-1-git-send-email-sathya.perla@emulex.com>
From: Vasundhara Volam <vasundhara.volam@emulex.com>
BE3 FW allocates VF resources for upto 30 VFs per PF while a max value of 32
may be reported via PCI config space. Fix this in the driver.
Signed-off-by: Vasundhara Volam <vasundhara.volam@emulex.com>
Signed-off-by: Sathya Perla <sathya.perla@emulex.com>
---
drivers/net/ethernet/emulex/benet/be.h | 1 +
drivers/net/ethernet/emulex/benet/be_main.c | 2 ++
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/net/ethernet/emulex/benet/be.h b/drivers/net/ethernet/emulex/benet/be.h
index d266c86..5b622993 100644
--- a/drivers/net/ethernet/emulex/benet/be.h
+++ b/drivers/net/ethernet/emulex/benet/be.h
@@ -110,6 +110,7 @@ static inline char *nic_name(struct pci_dev *pdev)
#define MAX_RX_POST BE_NAPI_WEIGHT /* Frags posted at a time */
#define RX_FRAGS_REFILL_WM (RX_Q_LEN - MAX_RX_POST)
+#define MAX_VFS 30 /* Max VFs supported by BE3 FW */
#define FW_VER_LEN 32
struct be_dma_mem {
diff --git a/drivers/net/ethernet/emulex/benet/be_main.c b/drivers/net/ethernet/emulex/benet/be_main.c
index d86d25c..def2f66 100644
--- a/drivers/net/ethernet/emulex/benet/be_main.c
+++ b/drivers/net/ethernet/emulex/benet/be_main.c
@@ -2723,6 +2723,8 @@ static int be_get_config(struct be_adapter *adapter)
if (pos) {
pci_read_config_word(adapter->pdev, pos + PCI_SRIOV_TOTAL_VF,
&dev_num_vfs);
+ if (!lancer_chip(adapter))
+ dev_num_vfs = min_t(u16, dev_num_vfs, MAX_VFS);
adapter->dev_num_vfs = dev_num_vfs;
}
return 0;
--
1.7.4
next prev parent reply other threads:[~2012-08-29 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1346222264-20819-1-git-send-email-sathya.perla@emulex.com>
2012-08-29 6:37 ` [net-next PATCH 1/5] be2net: create RSS rings even in multi-channel configs Sathya Perla
2012-08-29 6:37 ` Sathya Perla [this message]
2012-08-29 6:37 ` [net-next PATCH 3/5] be2net: fix FW default for VF tx-rate Sathya Perla
2012-08-29 6:37 ` [net-next PATCH 4/5] be2net: fixup malloc/free of adapter->pmac_id Sathya Perla
2012-08-29 6:37 ` [net-next PATCH 5/5] be2net: modify log msg for lack of privilege error Sathya Perla
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=3d88682f-40e6-48ec-b183-e768d4340c4b@exht1.ad.emulex.com \
--to=sathya.perla@emulex.com \
--cc=netdev@vger.kernel.org \
--cc=vasundhara.volam@emulex.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