From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Deng, KaiwenX" <kaiwenx.deng@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"Zhou, YidingX" <yidingx.zhou@intel.com>,
"Deng, KaiwenX" <kaiwenx.deng@intel.com>,
"Wang, Haiyue" <haiyue.wang@intel.com>,
Dongdong Liu <liudongdong3@huawei.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [PATCH v2] net/ixgbe: fix error of drop queue index
Date: Fri, 11 Nov 2022 08:56:57 +0000 [thread overview]
Message-ID: <DM4PR11MB5994278B5D3D95531FEDBD6FD7009@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221111063930.101441-1-kaiwenx.deng@intel.com>
> -----Original Message-----
> From: Kaiwen Deng <kaiwenx.deng@intel.com>
> Sent: Friday, November 11, 2022 2:39 PM
> To: dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; Zhou, YidingX
> <yidingx.zhou@intel.com>; Deng, KaiwenX <kaiwenx.deng@intel.com>;
> Wang, Haiyue <haiyue.wang@intel.com>; Dongdong Liu
> <liudongdong3@huawei.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>
> Subject: [PATCH v2] net/ixgbe: fix error of drop queue index
>
> The drop queue index was not set when adding internal Flow Director
> Configuration copy in ixgbe device private data.
> Therefore dropped packets would be received by queue 0 which is set to
> drop queue.
>
> This commit sets drop queue index as IXGBE_FDIR_DROP_QUEUE to fix this
> issue.
>
> Fixes: 5007ac13189d ("ethdev: remove deprecated Flow Director
> configuration")
>
> Signed-off-by: Kaiwen Deng <kaiwenx.deng@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2022-11-11 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 8:48 [PATCH] " kevin-intel
2022-11-08 1:07 ` Zhang, Qi Z
2022-11-11 6:39 ` [PATCH v2] " Kaiwen Deng
2022-11-11 8:56 ` Zhang, Qi Z [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=DM4PR11MB5994278B5D3D95531FEDBD6FD7009@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=kaiwenx.deng@intel.com \
--cc=liudongdong3@huawei.com \
--cc=qiming.yang@intel.com \
--cc=yidingx.zhou@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).