From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: Ori Kam <orika@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
"techboard@dpdk.org" <techboard@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>,
Ivan Malov <ivan.malov@arknetworks.am>
Subject: Re: [RFC] lib/ethdev: introduce table driven APIs
Date: Fri, 16 Jun 2023 06:50:00 +0530 [thread overview]
Message-ID: <CALBAE1PybftuVVCdFH393sLyyj-1_ics7Otrc9MnX2iOjwum1w@mail.gmail.com> (raw)
In-Reply-To: <DM4PR11MB59941C1EB54D16E750E6CD2DD75BA@DM4PR11MB5994.namprd11.prod.outlook.com>
On Thu, Jun 15, 2023 at 7:36 PM Zhang, Qi Z <qi.z.zhang@intel.com> wrote:
>
> > > If we assume that the application is not P4-aware, it will consume existing
> > rte_flow API for flow offloading. In this case, all we need to do is implement
> > it in the PMD, which will be a highly hardware-specific task. Do you propose
> > generalizing this common part?
> > >
> > > On the other hand, if the application is P4-aware, we can assume that
> > there won't be a need for translation between P4 tokens and rte_flow
> > protocols in the PMD.
> >
> > I agree, Translation is BAD. There are two elements to that.
> > 1)if it is p4 aware application, why bother with DPDK abstraction?
> > 2)Can we use compiler techniques to avoid the cost of translation if P4-
> > aware path is needed in DPDK. Rather than creating yet another library. In
> > this context, that would translate to some of your compiler and FW work
> > making as generic so that _any_ other rte_flow based driver can use and
> > improve it.
>
>
> Ok, I would like to gain a better understanding. Below is my current understanding:
>
> There are no plans to introduce any new API from DPDK. However, your proposal suggests the creation of a tool, such as a compiler, which would assist in generating a translation layer from P4 table/actions to rte_flow for user application like p4 runtime backend that based on DPDK.
>
> Could you provide more details about the design? Specifically, I would like to know what the input for the compiler is and who is responsible for generating that input, as well as the process involved.
>
> I apologize if I have not grasped the complete picture, but I would appreciate your patience.
+ @Cristian Dumitrescu
There is already a lot of p4(just based on DPDK lib/pipeline SW, not
with any HW acceleration) with DPDK. Not sure how much it overlaps,
and how clean is this to integrate with existing SW or "create new
one"?
I would think, enhancing the current p4-dpdk support by using rte_flow
backend. That would translate to
1) Update https://github.com/p4lang/p4c/tree/main/backends/dpdk to
understand generic p4 table key token to rte_flow token for spec file
generation.
2) Update https://github.com/p4lang/p4-dpdk-target or introduce common
library in DPDK to map compiler output (spec file) to rte_flow objects
invocations.
next prev parent reply other threads:[~2023-06-16 1:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 11:15 Qi Zhang
2023-06-12 15:32 ` Ivan Malov
2023-06-13 3:48 ` Zhang, Qi Z
2023-06-13 6:38 ` Ivan Malov
2023-06-14 5:42 ` Zhang, Qi Z
2023-06-14 18:30 ` Ori Kam
2023-06-15 2:25 ` Zhang, Qi Z
2023-06-15 4:57 ` Jerin Jacob
2023-06-15 6:03 ` Zhang, Qi Z
2023-06-15 6:21 ` Jerin Jacob
2023-06-15 7:42 ` Zhang, Qi Z
2023-06-15 8:37 ` Jerin Jacob
2023-06-15 13:25 ` Zhang, Qi Z
2023-06-16 1:20 ` Jerin Jacob [this message]
2023-06-19 0:22 ` Zhang, Qi Z
2023-06-19 9:52 ` Jerin Jacob
2023-06-20 1:52 ` Zhang, Qi Z
2023-06-20 5:06 ` Jerin Jacob
2023-06-20 11:10 ` Ori Kam
2023-07-19 13:39 ` Dumitrescu, Cristian
2023-08-02 9:31 ` Dumitrescu, Cristian
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=CALBAE1PybftuVVCdFH393sLyyj-1_ics7Otrc9MnX2iOjwum1w@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=helin.zhang@intel.com \
--cc=ivan.malov@arknetworks.am \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.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).