From: "Singh, Aman Deep" <aman.deep.singh@intel.com>
To: "Huang, ZhiminX" <zhiminx.huang@intel.com>,
"Ye, MingjinX" <mingjinx.ye@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Zhou, YidingX" <yidingx.zhou@intel.com>,
"Zhang, Yuying" <yuying.zhang@intel.com>
Subject: Re: [PATCH v4 1/2] app/testpmd: fix vlan offload of rxq
Date: Thu, 27 Oct 2022 18:46:30 +0530 [thread overview]
Message-ID: <9cdce4d4-f1f4-409b-bc30-2cf4c5da6bf1@intel.com> (raw)
In-Reply-To: <BN0PR11MB5712EFDC8E9E3E66BE604014FD339@BN0PR11MB5712.namprd11.prod.outlook.com>
On 10/27/2022 2:06 PM, Huang, ZhiminX wrote:
>> -----Original Message-----
>> From: Mingjin Ye <mingjinx.ye@intel.com>
>> Sent: Thursday, October 27, 2022 1:10 AM
>> To: dev@dpdk.org
>> Cc: stable@dpdk.org; Zhou, YidingX <yidingx.zhou@intel.com>; Ye, MingjinX
>> <mingjinx.ye@intel.com>; Singh, Aman Deep <aman.deep.singh@intel.com>;
>> Zhang, Yuying <yuying.zhang@intel.com>
>> Subject: [PATCH v4 1/2] app/testpmd: fix vlan offload of rxq
>>
>> After setting vlan offload in testpmd, the result is not updated to rxq. Therefore,
>> the queue needs to be reconfigured after executing the "vlan offload" related
>> commands.
>>
>> Fixes: a47aa8b97afe ("app/testpmd: add vlan offload support")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
Acked-by: Aman Singh<aman.deep.singh@intel.com>
>> ---
> Tested-by: Zhimin Huang <zhiminx.huang@intel.com >
>
>
next prev parent reply other threads:[~2022-10-27 13:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 17:10 Mingjin Ye
2022-10-26 9:52 ` lihuisong (C)
2022-10-27 11:02 ` Ye, MingjinX
2022-10-28 2:09 ` lihuisong (C)
2022-11-03 1:28 ` Ye, MingjinX
2022-11-03 7:01 ` lihuisong (C)
2022-11-04 8:21 ` Ye, MingjinX
2022-11-04 10:17 ` lihuisong (C)
2022-11-04 11:33 ` Ye, MingjinX
2022-11-06 10:32 ` Andrew Rybchenko
2022-11-07 7:18 ` Ye, MingjinX
2022-10-26 17:10 ` [PATCH v4 2/2] net/ice: fix vlan offload Mingjin Ye
2022-10-27 8:36 ` Huang, ZhiminX
2022-10-27 8:36 ` [PATCH v4 1/2] app/testpmd: fix vlan offload of rxq Huang, ZhiminX
2022-10-27 13:16 ` Singh, Aman Deep [this message]
2022-11-08 13:28 ` [PATCH v5 1/2] net/ice: fix vlan offload Mingjin Ye
2022-11-08 13:28 ` [PATCH v5 2/2] net/ice: fix vlan offload of rxq Mingjin Ye
2022-11-09 1:52 ` Huang, ZhiminX
2022-11-21 2:54 ` [PATCH v6] doc: add PMD known issue Mingjin Ye
2022-11-25 1:55 ` Ye, MingjinX
2022-12-09 10:20 ` Ye, MingjinX
2022-12-13 1:41 ` Zhang, Qi Z
2022-12-13 4:25 ` Ye, MingjinX
2022-12-23 7:32 ` [PATCH v7] " Mingjin Ye
2022-12-26 2:52 ` Mingjin Ye
2022-12-27 9:00 ` Mingjin Ye
2022-12-27 16:40 ` Stephen Hemminger
2023-01-28 6:01 ` [PATCH v8] " Mingjin Ye
2023-01-28 17:17 ` Stephen Hemminger
2023-02-02 2:30 ` Ye, MingjinX
2022-11-09 1:51 ` [PATCH v5 1/2] net/ice: fix vlan offload Huang, ZhiminX
2022-11-11 3:34 ` Ye, MingjinX
-- strict thread matches above, loose matches on Subject: below --
2022-10-27 11:09 [PATCH v4 1/2] app/testpmd: fix vlan offload of rxq Ye, MingjinX
2022-10-24 17:27 Mingjin Ye
2022-10-24 16:24 Mingjin Ye
2022-10-24 15:44 Mingjin Ye
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=9cdce4d4-f1f4-409b-bc30-2cf4c5da6bf1@intel.com \
--to=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=mingjinx.ye@intel.com \
--cc=stable@dpdk.org \
--cc=yidingx.zhou@intel.com \
--cc=yuying.zhang@intel.com \
--cc=zhiminx.huang@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).