From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Beilei Xing <beilei.xing@intel.com>, jingjing.wu@intel.com
Cc: helin.zhang@intel.com, bernard.iremonger@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6 0/4] add support for MPLS tunnel filter
Date: Thu, 30 Mar 2017 18:04:59 +0100 [thread overview]
Message-ID: <d9386c2c-546a-1005-8a41-1000bdd4ee8d@intel.com> (raw)
In-Reply-To: <1490862594-139036-1-git-send-email-beilei.xing@intel.com>
On 3/30/2017 9:29 AM, Beilei Xing wrote:
> This patchset adds support for MPLSoGRE and MPLSoUDP
> tunnel filters.
> I40e NICs can't recongnize MPLS tunnel packets by
> default, so need to load a profile to FW first, then
> MPLS tunnel packets can be recongnized with packet
> type 61 and 63.
> It depends on pipeline personalization profile support
> and changes of tunnel filter function.
>
> v6 changes:
> Change MPLS configuration with the FW modification.
>
> v5 changes:
> Rework MPLS parse function.
> Add replace filter flag for MPLS.
>
> v4 changes:
> Move replace functions to i40e_ethdev.c.
>
> v3 changes:
> Add big_buffer condition to this patchset.
> Change some descriptions for new MPLS and GRE items.
> Fix default mask error for MPLS label.
>
> Beilei Xing (4):
> ethdev: add MPLS and GRE items
> app/testpmd: add MPLS and GRE fields to flow command
> net/i40e: add MPLS parsing function
> net/i40e: enable tunnel filter for MPLS
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-03-30 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 8:29 Beilei Xing
2017-03-30 8:29 ` [dpdk-dev] [PATCH v6 1/4] ethdev: add MPLS and GRE items Beilei Xing
2017-03-30 8:29 ` [dpdk-dev] [PATCH v6 2/4] app/testpmd: add MPLS and GRE fields to flow command Beilei Xing
2017-03-30 8:29 ` [dpdk-dev] [PATCH v6 3/4] net/i40e: add MPLS parsing function Beilei Xing
2017-03-30 8:29 ` [dpdk-dev] [PATCH v6 4/4] net/i40e: enable tunnel filter for MPLS Beilei Xing
2017-03-30 17:04 ` Ferruh Yigit [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=d9386c2c-546a-1005-8a41-1000bdd4ee8d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@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).