[dpdk-dev] [PATCH v5 1/2] net/i40e: support VF request more queues

Zhang, Qi Z qi.z.zhang at intel.com
Tue Dec 18 02:44:49 CET 2018

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Monday, December 17, 2018 10:28 PM
> To: Yan, Zhirun <zhirun.yan at intel.com>; dev at dpdk.org; Zhang, Qi Z
> <qi.z.zhang at intel.com>
> Cc: Wang, Haiyue <haiyue.wang at intel.com>
> Subject: Re: [dpdk-dev] [PATCH v5 1/2] net/i40e: support VF request more
> queues
> On 12/17/2018 11:10 AM, Zhirun Yan wrote:
> > Before this patch, VF gets a default number of queues from the PF.
> > This patch enables VF to request a different number. When VF
> > configures more queues, it will send VIRTCHNL_OP_REQUEST_QUEUES to PF
> > to request more queues, if success, PF will reset the VF.
> >
> > User can run "port stop all", "port config port_id rxq/txq queue_num"
> > and "port start all" to reconfigure queue number.
> Is this replaces "ETH_I40E_QUEUE_NUM_PER_VF_ARG (queue-num-per-vf)"
> devarg?
> Should we remove this devarg?

queue-num-per-vf is the reserved queue number by PF for VF, it fit the situation when fixed queue number is required, so I think we still can keep it.
but I think the document could be modified properly , since queue-num-per-vf is never be the upper boundary of the queue number per vf, 
pf still can allocate max to 16 queues to exceed, we can add this explanation.

> >
> > Signed-off-by: Zhirun Yan <zhirun.yan at intel.com>
> > Signed-off-by: Haiyue Wang <haiyue.wang at intel.com>
> <...>

More information about the dev mailing list