From: Raslan Darawsheh <rasland@nvidia.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v6] ethdev: add new ext hdr for gtp psc
Date: Thu, 8 Jul 2021 09:27:31 +0000 [thread overview]
Message-ID: <DM4PR12MB5054A5A3F2342B580966BF1CCF199@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <c2499ccc-6e0e-9a54-91a6-0655796faa94@oktetlabs.ru>
Thank you for the review,
Basically it's not used yet since it will break the abi
The main usage was in rte_flow item of gtp_psc
To replace the current structure with the header definition. And since this will break the abi I'm adding the header definition now but will be used later in rte_flow.
Kindest regards,
Raslan Darawsheh
________________________________
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Sent: Thursday, July 8, 2021, 12:23 PM
To: Raslan Darawsheh; Singh, Aman Deep; dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6] ethdev: add new ext hdr for gtp psc
Hi Raslan,
On 7/6/21 5:24 PM, Raslan Darawsheh wrote:
> Hi Guys,
>
> Sorry for missing this mail, for some reason it was missed in my inbox,
> This is the link to this rfc:
> https://www.3gpp.org/ftp/Specs/archive/38_series/38.415/38415-g30.zip
Thanks for the link. The patch LGTM, but I have only one question left.
Where is it used? Are you going to upstream corresponding code in
the release cycle?
Andrew.
> Kindest regards,
> Raslan Darawsheh
>
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Andrew Rybchenko
>> Sent: Thursday, July 1, 2021 5:06 PM
>> To: Singh, Aman Deep <aman.deep.singh@intel.com>; dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH v6] ethdev: add new ext hdr for gtp psc
>>
>> Hi Raslan,
>>
>> could you reply, please.
>>
>> Andrew.
>>
>> On 6/22/21 10:27 AM, Singh, Aman Deep wrote:
>>> Hi Raslan,
>>>
>>> Can you please provide link to this RFC 38415-g30 I just had some
>>> doubt on byte-order conversion as per RFC 1700
>>> <https://tools.ietf.org/html/rfc1700>
>>>
>>> Regards
>>> Aman
next prev parent reply other threads:[~2021-07-08 9:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:17 Raslan Darawsheh
2021-06-22 7:27 ` Singh, Aman Deep
2021-07-01 14:06 ` Andrew Rybchenko
2021-07-06 14:24 ` Raslan Darawsheh
2021-07-08 9:23 ` Andrew Rybchenko
2021-07-08 9:27 ` Raslan Darawsheh [this message]
2021-07-08 9:39 ` Andrew Rybchenko
2021-07-08 10:29 ` Thomas Monjalon
2021-07-08 9:52 ` Singh, Aman Deep
2021-07-08 9:26 ` Andrew Rybchenko
2021-08-23 10:55 ` [dpdk-dev] [PATCH v7 0/2] update gtp psc to use net hdr Raslan Darawsheh
2021-08-23 10:55 ` [dpdk-dev] [PATCH v7 1/2] net: add new ext hdr for gtp psc Raslan Darawsheh
2021-09-07 10:30 ` Ferruh Yigit
2021-08-23 10:55 ` [dpdk-dev] [PATCH v7 2/2] ethdev: use ext hdr for gtp psc item Raslan Darawsheh
2021-09-07 10:30 ` Ferruh Yigit
2021-09-28 10:37 ` [dpdk-dev] [PATCH v7 0/2] update gtp psc to use net hdr Ferruh Yigit
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=DM4PR12MB5054A5A3F2342B580966BF1CCF199@DM4PR12MB5054.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
/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).