From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ori Kam <orika@nvidia.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"jerinjacobk@gmail.com" <jerinjacobk@gmail.com>,
"mb@smartsharesystems.com" <mb@smartsharesystems.com>,
"helin.zhang@intel.com" <helin.zhang@intel.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"john.mcnamara@intel.com" <john.mcnamara@intel.com>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>,
"qi.z.zhang@intel.com" <qi.z.zhang@intel.com>
Subject: Re: [PATCH V2] ethdev: add flow API support for P4-programmable devices
Date: Thu, 28 Sep 2023 10:19:40 +0100 [thread overview]
Message-ID: <96261d6d-69e3-49f0-8462-bf7894afe29c@amd.com> (raw)
In-Reply-To: <MW2PR12MB4666D300AA9899268FDAE27BD6C3A@MW2PR12MB4666.namprd12.prod.outlook.com>
On 9/26/2023 10:25 AM, Ori Kam wrote:
> Hi,
>
>> -----Original Message-----
>> From: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
>> Sent: Monday, September 25, 2023 3:34 PM
>> Subject: [PATCH V2] ethdev: add flow API support for P4-programmable
>> devices
>>
>> This patch introduces the new "program" action type to enable flow API
>> support for P4-programmable devices.
>>
>> In the case of P4-programmable devices, the device is initially blank.
>> The flow items and actions are defined by the user (outside of any
>> vendor control) through the P4 program, which is typically compiled
>> into firmware that is loaded on the device at init time. These flow
>> items and actions are then used during the run-time phase to add flows
>> on the device.
>>
>> Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
>> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
>>
>
>
> Acked-by: Ori Kam <orika@nvidia.com>
>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-09-28 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 18:59 [PATCH] " Cristian Dumitrescu
2023-09-21 16:38 ` Ori Kam
2023-09-25 11:52 ` Dumitrescu, Cristian
2023-09-25 12:35 ` Morten Brørup
2023-09-25 12:33 ` [PATCH V2] " Cristian Dumitrescu
2023-09-26 9:25 ` Ori Kam
2023-09-28 9:19 ` Ferruh Yigit [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=96261d6d-69e3-49f0-8462-bf7894afe29c@amd.com \
--to=ferruh.yigit@amd.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=john.mcnamara@intel.com \
--cc=mb@smartsharesystems.com \
--cc=orika@nvidia.com \
--cc=qi.z.zhang@intel.com \
--cc=techboard@dpdk.org \
--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).