DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "Cui, LunyuanX" <lunyuanx.cui@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: enable multi-queue Rx interrupt for VF
Date: Tue, 24 Dec 2019 10:53:46 +0800	[thread overview]
Message-ID: <20191224025346.GF14498@intel.com> (raw)
In-Reply-To: <039ED4275CED7440929022BC67E7061153DF2724@SHSMSX105.ccr.corp.intel.com>

On 12/24, Zhang, Qi Z wrote:
>
>
>> -----Original Message-----
>> From: Cui, LunyuanX <lunyuanx.cui@intel.com>
>> Sent: Tuesday, December 3, 2019 7:44 PM
>> To: dev@dpdk.org
>> Cc: Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
>> Yang, Qiming <qiming.yang@intel.com>; Cui, LunyuanX
>> <lunyuanx.cui@intel.com>
>> Subject: [PATCH] net/i40e: enable multi-queue Rx interrupt for VF
>> 
>> Current implementation is that only one Rx queue can support interrupt,
>> because all queues are mapped in the same vector id in vfio_enable_msix().
>> So VF can not support multi-queue Rx interrupt in the interrupt mode.
>> 
>> In this patch, if the packet I/O interrupt on datapath is enabled
>> (rte_intr_dp_is_en(intr_handle) is true), we map different interrupt vectors to
>> each queue and send this map to PF.
>> After PF sets the map to the register,
>> all Rx queue interrupts will be received.
>> 
>> In addition, vector id should less than the maximum vector value.
>> When queue number is more than vector value, we set up a loop of interrupt
>> vectors map.
>> 
>> Signed-off-by: Lunyuan Cui <lunyuanx.cui@intel.com>
>
>Acked-by: Qi Zhang <qi.z.zhang@intel.com>
>


Applied to dpdk-next-net-intel, Thanks.

      reply	other threads:[~2019-12-24  2:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 11:43 Lunyuan Cui
2019-12-24  1:40 ` Zhang, Qi Z
2019-12-24  2:53   ` Ye Xiaolong [this message]

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=20191224025346.GF14498@intel.com \
    --to=xiaolong.ye@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=lunyuanx.cui@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@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).