From: Ye Xiaolong <xiaolong.ye@intel.com>
To: "lunyuan.cui" <lunyuanx.cui@intel.com>
Cc: dev@dpdk.org, Wenzhuo Lu <wenzhuo.lu@intel.com>, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/iavf: fix multi-queue Rx interrupt for VF
Date: Thu, 5 Sep 2019 20:16:19 +0800 [thread overview]
Message-ID: <20190905121619.GG70700@intel.com> (raw)
In-Reply-To: <20190905032240.23239-1-lunyuanx.cui@intel.com>
On 09/05, lunyuan.cui wrote:
>The original issue was that the last queue could not
>be mapped to the interrupt vector, so the last queue
>could not receive the package in the interrupt mode.
>This patch fix the issue.
s/fix/fixes
>
>Fixes: d6bde6b5ea ("net/avf: enable Rx interrupt")
The convention is to have the 12 characters of commit SHA in Fixes tag.
>Cc: stable@dpdk.org
>
>Signed-off-by: lunyuan.cui <lunyuanx.cui@intel.com>
Signature format should be
Signed-off-by: Lunyuan Cui <lunyuanx.cui@intel.com>
Thanks,
Xiaolong
>---
> drivers/net/iavf/iavf_ethdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/net/iavf/iavf_ethdev.c b/drivers/net/iavf/iavf_ethdev.c
>index 8f3907378..6559bfa1f 100644
>--- a/drivers/net/iavf/iavf_ethdev.c
>+++ b/drivers/net/iavf/iavf_ethdev.c
>@@ -360,7 +360,7 @@ static int iavf_config_rx_queues_irqs(struct rte_eth_dev *dev,
> for (i = 0; i < dev->data->nb_rx_queues; i++) {
> vf->rxq_map[vec] |= 1 << i;
> intr_handle->intr_vec[i] = vec++;
>- if (vec >= vf->nb_msix)
>+ if (vec > vf->nb_msix)
> vec = IAVF_RX_VEC_START;
> }
> PMD_DRV_LOG(DEBUG,
>--
>2.17.1
>
next prev parent reply other threads:[~2019-09-05 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 3:22 lunyuan.cui
2019-09-05 12:16 ` Ye Xiaolong [this message]
2019-09-06 11:47 ` [dpdk-dev] [PATCH v2] " lunyuan.cui
2019-09-11 2:53 ` Yang, Qiming
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=20190905121619.GG70700@intel.com \
--to=xiaolong.ye@intel.com \
--cc=dev@dpdk.org \
--cc=lunyuanx.cui@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@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).