From: Thomas Monjalon <thomas@monjalon.net>
To: Alexander Kozyrev <akozyrev@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ori Kam <orika@nvidia.com>,
"nithind1988@gmail.com" <nithind1988@gmail.com>,
"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
Matan Azrad <matan@nvidia.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"rbhansali@marvell.com" <rbhansali@marvell.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: Re: [PATCH] mbuf: add transport mode ESP packet type
Date: Sat, 09 Nov 2024 12:50:40 +0100 [thread overview]
Message-ID: <5243201.taCxCBeP46@thomas> (raw)
In-Reply-To: <CH3PR12MB84605B1D0FB7469193E192CBA4452@CH3PR12MB8460.namprd12.prod.outlook.com>
15/10/2024 16:40, Dariusz Sosnowski:
> > -----Original Message-----
> > From: Alexander Kozyrev <akozyrev@nvidia.com>
> > Sent: Thursday, August 22, 2024 17:32
> > To: dev@dpdk.org
> > Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>; Ori Kam <orika@nvidia.com>;
> > nithind1988@gmail.com; olivier.matz@6wind.com; NBU-Contact-Thomas
> > Monjalon (EXTERNAL) <thomas@monjalon.net>; Matan Azrad
> > <matan@nvidia.com>; jerinj@marvell.com; rbhansali@marvell.com;
> > ferruh.yigit@amd.com
> > Subject: [PATCH] mbuf: add transport mode ESP packet type
> >
> > Support the IP Encapsulating Security Payload (ESP) in transport mode.
> > Currently, we have RTE_PTYPE_TUNNEL_ESP for the ESP tunnel mode.
> > Transport mode can be detected by parsing the "Next Header" field.
> > The Next Header is TCP for the transport mode and IP for the tunnel mode.
> > Add RTE_PTYPE_L4_ESP for the regular transport mode and
> > RTE_PTYPE_INNER_L4_ESP for the ESP over UDP packets.
> >
> > Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
>
> Reviewed-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Applied, thanks.
next prev parent reply other threads:[~2024-11-09 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 15:32 [PATCH] mbuf: add transport mode ESP packet type Alexander Kozyrev
2024-09-02 8:43 ` Nithin Dabilpuram
2024-09-04 21:09 ` Alexander Kozyrev
2024-10-15 14:40 ` Dariusz Sosnowski
2024-11-09 11:50 ` Thomas Monjalon [this message]
2024-10-17 20:47 ` Thomas Monjalon
2024-10-18 13:44 ` David Marchand
2024-10-22 13:19 ` Alexander Kozyrev
2024-10-23 4:54 ` Nithin Dabilpuram
2024-10-24 19:30 ` Alexander Kozyrev
2024-10-24 23:32 ` Ajit Khaparde
2024-10-29 14:48 ` Ori Kam
2024-10-29 18:41 ` Ajit Khaparde
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=5243201.taCxCBeP46@thomas \
--to=thomas@monjalon.net \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=ferruh.yigit@amd.com \
--cc=jerinj@marvell.com \
--cc=matan@nvidia.com \
--cc=nithind1988@gmail.com \
--cc=olivier.matz@6wind.com \
--cc=orika@nvidia.com \
--cc=rbhansali@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.