From: Jiang Mao <maox.jiang@intel.com>
To: xiaolong.ye@intel.com
Cc: dev@dpdk.org, Jiang Mao <maox.jiang@intel.com>
Subject: [dpdk-dev] [PATCH 2/2] net/i40e: fix fdir allocating msix resource error
Date: Tue, 9 Jun 2020 09:37:12 +0800 [thread overview]
Message-ID: <20200609013712.27026-2-maox.jiang@intel.com> (raw)
In-Reply-To: <20200609013712.27026-1-maox.jiang@intel.com>
Fdir allocating msix resource is not strictly necessary, if no resource left, print a warning message.
Signed-off-by: Jiang Mao <maox.jiang@intel.com>
Fixes: 4861cde461 (i40e: new poll mode driver)
---
drivers/net/i40e/i40e_ethdev.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/net/i40e/i40e_ethdev.c b/drivers/net/i40e/i40e_ethdev.c
index 33ed556c8..acc43077d 100644
--- a/drivers/net/i40e/i40e_ethdev.c
+++ b/drivers/net/i40e/i40e_ethdev.c
@@ -5744,6 +5744,17 @@ i40e_vsi_setup(struct i40e_pf *pf,
vsi->nb_msix = RTE_MIN(vsi->nb_qps,
RTE_MAX_RXTX_INTR_VEC_ID);
}
+ } else if (type == I40E_VSI_FDIR) {
+ ret = i40e_res_pool_alloc(&pf->msix_pool, 1);
+ if (ret < 0) {
+ PMD_DRV_LOG(WARNING, "MSIX vectors used up, FDIR can`t bind interrupt");
+ vsi->msix_intr = 0;
+ vsi->nb_msix = 0;
+ } else {
+ vsi->msix_intr = ret;
+ vsi->nb_msix = 1;
+ }
+
} else if (type != I40E_VSI_SRIOV) {
ret = i40e_res_pool_alloc(&pf->msix_pool, 1);
if (ret < 0) {
--
2.17.1
next prev parent reply other threads:[~2020-06-09 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 1:37 [dpdk-dev] [PATCH 1/2] net/i40e: fix binding interrupt without msix vectors Jiang Mao
2020-06-09 1:37 ` Jiang Mao [this message]
2020-06-09 2:02 ` Ye Xiaolong
2020-06-09 2:25 Jiang Mao
2020-06-09 2:25 ` [dpdk-dev] [PATCH 2/2] net/i40e: fix fdir allocating msix resource error Jiang Mao
2020-06-17 5:43 ` Huang, ZhiminX
2020-07-08 19:52 ` Jiang Mao
2020-07-20 10:31 ` Zhang, Qi Z
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=20200609013712.27026-2-maox.jiang@intel.com \
--to=maox.jiang@intel.com \
--cc=dev@dpdk.org \
--cc=xiaolong.ye@intel.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).