From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Ori Kam <orika@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [PATCH 1/6] ethdev: add modify IPv4 next protocol field
Date: Wed, 7 Feb 2024 11:31:38 +0000 [thread overview]
Message-ID: <IA1PR12MB8311FA4E6BF78F3F46E6AFCFA4452@IA1PR12MB8311.namprd12.prod.outlook.com> (raw)
In-Reply-To: <MW2PR12MB4666C6E0FC34CDC4A9B2E3B2D6462@MW2PR12MB4666.namprd12.prod.outlook.com>
> -----Original Message-----
> From: Ori Kam <orika@nvidia.com>
> Sent: Tuesday, February 6, 2024 14:01
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Dariusz Sosnowski <dsosnowski@nvidia.com>
> Subject: RE: [PATCH 1/6] ethdev: add modify IPv4 next protocol field
>
> Hi Slava
>
> > -----Original Message-----
> > From: Slava Ovsiienko <viacheslavo@nvidia.com>
> > Sent: Tuesday, February 6, 2024 2:18 PM <dsosnowski@nvidia.com>
> > Subject: [PATCH 1/6] ethdev: add modify IPv4 next protocol field
> >
> > Add IPv4 next protocol modify field definition.
> >
> > Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> > ---
> > doc/guides/rel_notes/release_24_03.rst | 1 +
> > lib/ethdev/rte_flow.h | 3 ++-
> > 2 files changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/doc/guides/rel_notes/release_24_03.rst
> > b/doc/guides/rel_notes/release_24_03.rst
> > index 2b91217943..33e9303ae1 100644
> > --- a/doc/guides/rel_notes/release_24_03.rst
> > +++ b/doc/guides/rel_notes/release_24_03.rst
> > @@ -64,6 +64,7 @@ New Features
> >
> > * Added ``RTE_FLOW_ITEM_TYPE_RANDOM`` to match random value.
> > * Added ``RTE_FLOW_FIELD_RANDOM`` to represent it in field ID struct.
> > + * Added ``RTE_FLOW_FIELD_IPV4_PROTO`` to represent it in field ID
> > struct.
> >
> > * ** Support for getting the number of used descriptors of a Tx
> > queue. **
> >
> > diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h index
> > 1267c146e5..84af730dc7 100644
> > --- a/lib/ethdev/rte_flow.h
> > +++ b/lib/ethdev/rte_flow.h
> > @@ -3933,7 +3933,8 @@ enum rte_flow_field_id {
> > RTE_FLOW_FIELD_IPV4_IHL, /**< IPv4 IHL. */
> > RTE_FLOW_FIELD_IPV4_TOTAL_LEN, /**< IPv4 total length. */
> > RTE_FLOW_FIELD_IPV6_PAYLOAD_LEN,/**< IPv6 payload length. */
> > - RTE_FLOW_FIELD_RANDOM /**< Random value. */
> > + RTE_FLOW_FIELD_RANDOM, /**< Random value. */
> > + RTE_FLOW_FIELD_IPV4_PROTO /**< IPv4 next protocol. */
> > };
> >
> > /**
> > --
> > 2.18.1
>
> Acked-by: Ori Kam <orika@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Best regards,
Dariusz Sosnowski
prev parent reply other threads:[~2024-02-07 11:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 12:17 Viacheslav Ovsiienko
2024-02-06 12:17 ` [PATCH 2/6] app/testpmd: add modify IPv4 next protocol command line Viacheslav Ovsiienko
2024-02-06 13:03 ` Ori Kam
2024-02-07 11:34 ` Dariusz Sosnowski
2024-02-06 12:17 ` [PATCH 3/6] net/mlx5: add modify IPv4 protocol implementation Viacheslav Ovsiienko
2024-02-07 11:36 ` Dariusz Sosnowski
2024-02-06 12:17 ` [PATCH 4/6] ethdev: add modify action support for IPsec fields Viacheslav Ovsiienko
2024-02-07 11:44 ` Dariusz Sosnowski
2024-02-06 12:17 ` [PATCH 5/6] app/testpmd: add modify ESP related fields command line Viacheslav Ovsiienko
2024-02-07 11:37 ` Dariusz Sosnowski
2024-02-06 12:17 ` [PATCH 6/6] net/mlx5: add modify field action IPsec support Viacheslav Ovsiienko
2024-02-07 11:45 ` Dariusz Sosnowski
2024-02-06 13:00 ` [PATCH 1/6] ethdev: add modify IPv4 next protocol field Ori Kam
2024-02-07 11:31 ` Dariusz Sosnowski [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=IA1PR12MB8311FA4E6BF78F3F46E6AFCFA4452@IA1PR12MB8311.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@nvidia.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).