From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>, <arybchenko@solarflare.com>
Cc: <dev@dpdk.org>, Hyong Youb Kim <hyonkim@cisco.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/enic: support GTP header flow matching
Date: Thu, 4 Nov 2021 11:36:02 +0000 [thread overview]
Message-ID: <64e97961-80cb-c598-1fe2-d84e3953fa6c@intel.com> (raw)
In-Reply-To: <20211028200424.4623-1-johndale@cisco.com>
On 10/28/2021 9:04 PM, John Daley wrote:
> The GTP, GTP-U, GTP-C header fields can be matched, however NIC does not
> support GTP tunneling so no items after the GTP header can be specified.
> If a GTP-U or GTP-C item is specified without a preceding UDP item, the
> UDP destination port is implicitly matched. For GTP, the destination UDP
> port must be specified but its value is not enforced.
>
> Signed-off-by: John Daley <johndale@cisco.com>
> Reviewed-by: Hyong Youb Kim <hyonkim@cisco.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-11-04 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 1:16 [dpdk-dev] [PATCH] " John Daley
2021-10-28 6:36 ` [dpdk-dev] [PATCH v2] " John Daley
2021-10-28 20:04 ` [dpdk-dev] [PATCH v3] " John Daley
2021-11-04 11:36 ` 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=64e97961-80cb-c598-1fe2-d84e3953fa6c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=hyonkim@cisco.com \
--cc=johndale@cisco.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).