DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Singh, Aman Deep" <aman.deep.singh@intel.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Ori Kam <orika@nvidia.com>, Yuying Zhang <yuying.zhang@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 2/2] app/testpmd: add GTP PSC QFI field support
Date: Wed, 21 Sep 2022 18:16:43 +0530	[thread overview]
Message-ID: <be98415b-59a7-ae66-f861-8b6474e23937@intel.com> (raw)
In-Reply-To: <20220921101839.1711058-3-dsosnowski@nvidia.com>



On 9/21/2022 3:48 PM, Dariusz Sosnowski wrote:
> This patch adds support for specifying GTP PSC QFI field as a source or
> destination of MODIFY_FIELD flow action in testpmd.
>
> An example for copying GTP PSC 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 PSC QFI 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: Aman Singh<aman.deep.singh@intel.com>
> ---
>


  reply	other threads:[~2022-09-21 12:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 10:18 [PATCH 0/2] ethdev: add GTP PSC QFI field 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 [this message]
2022-09-21 14:32 ` [PATCH v2] ethdev: add GTP PSC QFI field Dariusz Sosnowski
2022-09-26 14:57   ` Andrew Rybchenko

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=be98415b-59a7-ae66-f861-8b6474e23937@intel.com \
    --to=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=orika@nvidia.com \
    --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).