DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ori Kam <orika@mellanox.com>, Xiao Zhang <xiao.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [v2] ethdev: add PFCP header to flow API
Date: Tue, 10 Mar 2020 14:45:55 +0000	[thread overview]
Message-ID: <8c53515b-3b50-5987-32d1-43f1eb5fabf7@intel.com> (raw)
In-Reply-To: <AM6PR05MB5176E5B3F771EBA696CB99FCDBFE0@AM6PR05MB5176.eurprd05.prod.outlook.com>

On 3/9/2020 4:31 PM, Ori Kam wrote:
> 
> 
>> -----Original Message-----
>> From: Xiao Zhang <xiao.zhang@intel.com>
>> Sent: Friday, March 6, 2020 8:39 AM
>> To: dev@dpdk.org
>> Cc: Ori Kam <orika@mellanox.com>; ferruh.yigit@intel.com; Xiao Zhang
>> <xiao.zhang@intel.com>
>> Subject: [v2] ethdev: add PFCP header to flow API
>>
>> This patch adds the new flow item RTE_FLOW_ITEM_TYPE_PFCP to flow API to
>> match a PFCP header.
>> Add sample PFCP rules for testpmd guide. Since Session Endpoint
>> Identifier (SEID) only will be present in PFCP Session header and PFCP
>> Session headers shall be identified when the S field is equal to 1, when
>> create rules for PFCP Session header with certain SEID the S field need
>> be set 1.
>>
>> Signed-off-by: Xiao Zhang <xiao.zhang@intel.com>
> 
> Acked-by: Ori Kam <orika@mellanox.com>
> 

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2020-03-10 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20  4:02 [dpdk-dev] " Xiao Zhang
2020-03-03  8:48 ` Ori Kam
2020-03-06  6:48   ` Zhang, Xiao
2020-03-06  6:39 ` [dpdk-dev] [v2] " Xiao Zhang
2020-03-09 16:31   ` Ori Kam
2020-03-10 14:45     ` 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=8c53515b-3b50-5987-32d1-43f1eb5fabf7@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=orika@mellanox.com \
    --cc=xiao.zhang@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).