From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, Hyong Youb Kim <hyonkim@cisco.com>,
John Daley <johndale@cisco.com>
Subject: Re: [dpdk-dev] [PATCH] mbuf: clarify QINQ flag usage
Date: Tue, 2 Oct 2018 11:08:27 +0100 [thread overview]
Message-ID: <ccdfb532-bfe7-9c56-80dc-b9e872e75ce0@intel.com> (raw)
In-Reply-To: <c51146a4-2a8e-ca06-be3f-ccb0197073f9@solarflare.com>
On 10/2/2018 10:44 AM, Andrew Rybchenko wrote:
> On 10/2/18 1:17 PM, Ferruh Yigit wrote:
>> Update implementation that when PKT_RX_QINQ_STRIPPED mbuf ol_flags
>> set by PMD, PKT_RX_QINQ, PKT_RX_VLAN_STRIPPED & PKT_RX_VLAN
>> should be also set.
>>
>> Clarify mbuf documentations that when PKT_RX_QINQ set PKT_RX_VLAN also
>> should be set.
>>
>> So that appllication can rely on PKT_RX_QINQ flag to access both
>> mbuf.vlan_tci & mbuf.vlan_tci_outer
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>> ---
>> Cc: Hyong Youb Kim <hyonkim@cisco.com>
>> Cc: John Daley <johndale@cisco.com>
>> ---
>> app/test-pmd/rxonly.c | 2 +-
>> doc/guides/nics/features.rst | 7 ++++---
>> drivers/net/i40e/i40e_rxtx.c | 3 ++-
>> lib/librte_mbuf/rte_mbuf.c | 1 +
>> lib/librte_mbuf/rte_mbuf.h | 5 +++--
>> 5 files changed, 11 insertions(+), 7 deletions(-)
>>
>> diff --git a/app/test-pmd/rxonly.c b/app/test-pmd/rxonly.c
>> index a93d80612..08a5fc2cf 100644
>> --- a/app/test-pmd/rxonly.c
>> +++ b/app/test-pmd/rxonly.c
>> @@ -132,7 +132,7 @@ pkt_burst_receive(struct fwd_stream *fs)
>> printf(" - timestamp %"PRIu64" ", mb->timestamp);
>> if (ol_flags & PKT_RX_VLAN_STRIPPED)
>
> It looks like it should be PKT_RX_VLAN above.
There is already a patch from Hyong for it which triggered this patch:
https://patches.dpdk.org/patch/45350/
>
>> printf(" - VLAN tci=0x%x", mb->vlan_tci);
>> - if (ol_flags & PKT_RX_QINQ_STRIPPED)
>> + if (ol_flags & PKT_RX_QINQ)
>> printf(" - QinQ VLAN tci=0x%x, VLAN tci outer=0x%x",
>> mb->vlan_tci, mb->vlan_tci_outer);
>
> The first one duplicates above printout, so it should be either put before
> PKT_RX_VLAN check and do PKT_RX_VLAN in else branch, or simply removed
> from here.
Right, let me check it.
next prev parent reply other threads:[~2018-10-02 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 10:17 Ferruh Yigit
2018-10-02 9:44 ` Andrew Rybchenko
2018-10-02 10:08 ` Ferruh Yigit [this message]
2018-10-02 11:36 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-10-02 10:40 ` Andrew Rybchenko
2018-10-03 15:19 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2018-10-09 8:59 ` Olivier Matz
2018-10-09 9:48 ` Ferruh Yigit
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=ccdfb532-bfe7-9c56-80dc-b9e872e75ce0@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=hyonkim@cisco.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=johndale@cisco.com \
--cc=marko.kovacevic@intel.com \
--cc=olivier.matz@6wind.com \
--cc=qi.z.zhang@intel.com \
--cc=wenzhuo.lu@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).