From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id A8FE72BF4 for ; Tue, 2 Oct 2018 10:46:58 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Oct 2018 01:46:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,331,1534834800"; d="scan'208";a="267691427" Received: from fyigit-mobl.ger.corp.intel.com (HELO [10.237.221.49]) ([10.237.221.49]) by fmsmga005.fm.intel.com with ESMTP; 02 Oct 2018 01:46:56 -0700 To: Hyong Youb Kim Cc: John Daley , wenzhuo.lu@intel.com, jingjing.wu@intel.com, bernard.iremonger@intel.com, olivier.matz@6wind.com, dev@dpdk.org, beilei.xing@intel.com, qi.z.zhang@intel.com References: <20180926030617.6702-1-johndale@cisco.com> <20181002022958.GA14560@HYONKIM-7R0DR.cisco.com> From: Ferruh Yigit Openpgp: preference=signencrypt Message-ID: Date: Tue, 2 Oct 2018 09:46:54 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181002022958.GA14560@HYONKIM-7R0DR.cisco.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] app/testpmd: check Rx VLAN offload flag to print VLAN TCI X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2018 08:46:59 -0000 On 10/2/2018 3:29 AM, Hyong Youb Kim wrote: > On Mon, Oct 01, 2018 at 03:01:40PM +0100, Ferruh Yigit wrote: >> On 9/26/2018 4:06 AM, John Daley wrote: >>> From: Hyong Youb Kim >>> >>> Since the following commit, PKT_RX_VLAN indicates the presence of >>> mbuf's vlan_tci, not PKT_RX_VLAN_STRIPPED. >>> >>> commit 380a7aab1ae2 ("mbuf: rename deprecated VLAN flags") >>> Cc: olivier.matz@6wind.com >>> >>> Signed-off-by: Hyong Youb Kim >>> Reviewed-by: John Daley >>> --- >>> app/test-pmd/rxonly.c | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/app/test-pmd/rxonly.c b/app/test-pmd/rxonly.c >>> index a93d80612..e8d226624 100644 >>> --- a/app/test-pmd/rxonly.c >>> +++ b/app/test-pmd/rxonly.c >>> @@ -130,7 +130,7 @@ pkt_burst_receive(struct fwd_stream *fs) >>> } >>> if (ol_flags & PKT_RX_TIMESTAMP) >>> printf(" - timestamp %"PRIu64" ", mb->timestamp); >>> - if (ol_flags & PKT_RX_VLAN_STRIPPED) >>> + if (ol_flags & PKT_RX_VLAN) >>> printf(" - VLAN tci=0x%x", mb->vlan_tci); >>> if (ol_flags & PKT_RX_QINQ_STRIPPED) >>> printf(" - QinQ VLAN tci=0x%x, VLAN tci outer=0x%x", >> >> Isn't same also correct for QinQ, PKT_RX_QINQ means mb->vlan_tci & >> mb->vlan_tci_outer are set? >> > > That is a good point. > > According to rte_mbuf.h, PKT_RX_QINQ means "The RX packet is a double > VLAN, and the outer tci has been saved in in mbuf->vlan_tci_outer." > > Here is a summary. > PKT_RX_VLAN => vlan_tci is set > PKT_RX_QINQ => vlan_tci_outer is set Because of the comment on "PKT_RX_QINQ_STRIPPED" I think: PKT_RX_QINQ => vlan_tci_outer & vlan_tci is set Although it is not clear from "PKT_RX_QINQ" comment. > PKT_RX_VLAN_STRIPPED => must also set PKT_RX_VLAN > PKT_RX_QINQ_STRIPPED => must also set PKT_RX_VLAN, PKT_RX_QINQ, > PKT_RX_VLAN_STRIPPED > > Looks like i40e is the only driver that is using > PKT_RX_QINQ_STRIPPED. And, it does not set PKT_RX_QINQ. I am CC'ing > i40e maintainers. > > Back to rxonly.. > > + if (ol_flags & (PKT_RX_QINQ | PKT_RX_VLAN)) > printf(" - QinQ VLAN tci=0x%x, VLAN tci outer=0x%x", > mb->vlan_tci, mb->vlan_tci_outer); > > A change like this would be technically correct, but may break i40e > test cases. Or, if the above message is really meant for 'stripped', > then perhaps add comment or rephrase the message for now? > > As for the use of PKT_RX_VLAN, some drivers like enic and ixgbe can > set PKT_RX_VLAN independent of vlan stripping, which led me to writing > this patch. I think Olivier fixed all drivers when he introduced > PKT_RX_VLAN. So using PKT_RX_VLAN in rxonly shouldn't be breaking > anyone's test cases. +1 to PKT_RX_VLAN update. I was thinking PKT_RX_QINQ also can be fixed quickly in testpmd with this patch, taking into account that it may affect other piece of code, agree to get this patch as it is and consider QINQ changes in different patch.