From: Raslan Darawsheh <rasland@nvidia.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Ori Kam <orika@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: Re: [PATCH v2 1/1] ethdev: add IPv6 FL and TC field identifiers
Date: Wed, 14 Feb 2024 04:08:51 +0000 [thread overview]
Message-ID: <MN0PR12MB60566061C7FA92B5350208F9CF4E2@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240207155128.1581670-2-michaelba@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
HI,
> Add new "rte_flow_field_id" enumeration values to describe both IPv6
>traffic class and IPv6 flow label fields.
>
>The TC value is "RTE_FLOW_FIELD_IPV6_TRAFFIC_CLASS" in flow API and
>"ipv6_traffic_class" in testpmd command.
>The FL value is "RTE_FLOW_FIELD_IPV6_FLOW_LABEL" in flow API and
>"ipv6_flow_label" in testpmd command.
>Signed-off-by: Michael Baum <michaelba@nvidia.com>
>Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
[-- Attachment #2: Type: text/html, Size: 2793 bytes --]
prev parent reply other threads:[~2024-02-14 4:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 14:26 [PATCH 0/1] ethdev: add IPv6 " Michael Baum
2024-02-06 14:26 ` [PATCH 1/1] ethdev: add IPv6 FL and TC " Michael Baum
2024-02-07 13:47 ` Dariusz Sosnowski
2024-02-07 15:51 ` [PATCH v2 0/1] ethdev: add IPv6 " Michael Baum
2024-02-07 15:51 ` [PATCH v2 1/1] ethdev: add IPv6 FL and TC " Michael Baum
2024-02-08 22:37 ` Ferruh Yigit
2024-02-11 8:05 ` Michael Baum
2024-02-12 17:22 ` Ferruh Yigit
2024-02-12 17:23 ` Ferruh Yigit
2024-02-14 4:08 ` Raslan Darawsheh [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=MN0PR12MB60566061C7FA92B5350208F9CF4E2@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=ferruh.yigit@amd.com \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
/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).