All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Ting Xu <ting.xu@intel.com>
Cc: dev@dpdk.org, beilei.xing@intel.com, jingjing.wu@intel.com,
	stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] net/iavf: fix setting wrong RXDID value for Rx queue
Date: Mon, 18 May 2020 10:01:09 +0800	[thread overview]
Message-ID: <20200518020109.GB93932@intel.com> (raw)
In-Reply-To: <20200511152748.21144-1-ting.xu@intel.com>

On 05/11, Ting Xu wrote:
>CVL kernel PF configures all reserved queues for VF, including
>Rx queue RXDID. The number of reserved queues is the maximum
>between Tx and Rx queues. If the number of the enabled Rx queues
>is less than that of reserved queues, required RXDID will only
>be set for those enabled, but default value (0) is set for others.
>However, RXDID 0 (legacy 16byte descriptor) is not supported now,
>PF will return error when configuring those disabled VF queues.
>
>In this patch, required RXDID is set for all reserved Rx queues,
>no matter enabled or not. In this way, PF will configure Rx
>queues correctly without reporting error.
>
>Fixes: b8b4c54ef9b0 ("net/iavf: support flexible Rx descriptor in normal path")
>Cc: stable@dpdk.org

b8b4c54ef9b0 is introduce in this release, no need to cc stable.
>

Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>

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

      parent reply	other threads:[~2020-05-18  2:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 15:27 [dpdk-dev] [PATCH v1] net/iavf: fix setting wrong RXDID value for Rx queue Ting Xu
2020-05-15  3:29 ` Zeng, XiaoxiaoX
2020-05-18  2:01 ` 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=20200518020109.GB93932@intel.com \
    --to=xiaolong.ye@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=stable@dpdk.org \
    --cc=ting.xu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.