From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Ori Kam <orika@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@xilinx.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] ethdev: add GTP PSC QFI field
Date: Mon, 26 Sep 2022 17:57:13 +0300 [thread overview]
Message-ID: <599a0c5e-8c1c-85b4-2c14-2babeb39ba5f@oktetlabs.ru> (raw)
In-Reply-To: <20220921143202.1790802-1-dsosnowski@nvidia.com>
On 9/21/22 17:32, Dariusz Sosnowski wrote:
> This patch introduces the GTP PSC QFI modify field support and adds
> the testpmd CLI command support.
>
> An example for copying GTP QFI field using modify_field action:
>
> modify_field op set
> dst_type meta
> src_type gtp_psc_qfi
> width 8
>
> An example of setting GTP QFI field value to 0x1f using modify_field
> action:
>
> modify_field op set
> dst_type gtp_psc_qfi
> src_type value src_value 1f
> width 8
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
> ---
>
> v2:
>
> * Squashed ethdev and testpmd commits.
>
> app/test-pmd/cmdline_flow.c | 2 +-
> lib/ethdev/rte_flow.h | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-09-26 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 10:18 [PATCH 0/2] " Dariusz Sosnowski
2022-09-21 10:18 ` [PATCH 1/2] " Dariusz Sosnowski
2022-09-21 12:43 ` Ori Kam
2022-09-21 14:43 ` Dariusz Sosnowski
2022-09-21 10:18 ` [PATCH 2/2] app/testpmd: add GTP PSC QFI field support Dariusz Sosnowski
2022-09-21 12:46 ` Singh, Aman Deep
2022-09-21 14:32 ` [PATCH v2] ethdev: add GTP PSC QFI field Dariusz Sosnowski
2022-09-26 14:57 ` Andrew Rybchenko [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=599a0c5e-8c1c-85b4-2c14-2babeb39ba5f@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=ferruh.yigit@xilinx.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=yuying.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).