From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Raslan Darawsheh <rasland@mellanox.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: add parsing for multiple VLAN headers
Date: Tue, 21 Apr 2020 14:54:18 +0000 [thread overview]
Message-ID: <DM6PR11MB2537C638566FDD998B7ECEACEFD50@DM6PR11MB2537.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1587396746-409-1-git-send-email-rasland@mellanox.com>
> -----Original Message-----
> From: Raslan Darawsheh <rasland@mellanox.com>
> Sent: Monday, April 20, 2020 4:32 PM
> To: Iremonger, Bernard <bernard.iremonger@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: [PATCH] app/testpmd: add parsing for multiple VLAN headers
>
> When having multiple VLANs in the packet, parse_ethernet is cabable of
> parsing only the first vlan.
>
> add parsing for mutliple VLAN headers in the packet.
>
> Fixes: 51f694dd40f5 ("app/testpmd: rework checksum forward engine")
> Cc: stable@dpdk.org
>
> Signed-off-by: Raslan Darawsheh <rasland@mellanox.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
next prev parent reply other threads:[~2020-04-21 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 15:32 Raslan Darawsheh
2020-04-21 14:54 ` Iremonger, Bernard [this message]
2020-04-21 20:47 ` Ferruh Yigit
2020-04-22 11:05 ` Iremonger, Bernard
2020-04-22 11:28 ` Raslan Darawsheh
2020-04-22 7:22 ` Ori Kam
2020-04-23 8:41 ` [dpdk-dev] [PATCH v2] " Raslan Darawsheh
2020-04-23 8:59 ` Iremonger, Bernard
2020-04-23 9:01 ` Raslan Darawsheh
2020-04-23 9:05 ` [dpdk-dev] [PATCH v3] app/testpmd: add parsing for QINQ " Raslan Darawsheh
2020-04-24 16:35 ` 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=DM6PR11MB2537C638566FDD998B7ECEACEFD50@DM6PR11MB2537.namprd11.prod.outlook.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--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).