From: Ori Kam <orika@nvidia.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.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: Tue, 20 Jun 2023 11:10:57 +0000 [thread overview]
Message-ID: <MW2PR12MB46662EBE06125CBC68F7070DD65CA@MW2PR12MB4666.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1NW+iCvYo0tGUP7Pxi3i5-SGrW1icVTMTaBK7T9gtddTg@mail.gmail.com>
Hi
> -----Original Message-----
> From: Jerin Jacob <jerinjacobk@gmail.com>
> Sent: Tuesday, June 20, 2023 8:07 AM
>
> On Tue, Jun 20, 2023 at 7:22 AM Zhang, Qi Z <qi.z.zhang@intel.com> wrote:
> >
> >
> >
> > > -----Original Message-----
> > > From: Jerin Jacob <jerinjacobk@gmail.com>
> > > Sent: Monday, June 19, 2023 5:52 PM
> > > To: Zhang, Qi Z <qi.z.zhang@intel.com>
> > > Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Ori Kam
> > > <orika@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> > > <thomas@monjalon.net>; david.marchand@redhat.com; Richardson,
> Bruce
> > > <bruce.richardson@intel.com>; jerinj@marvell.com;
> ferruh.yigit@amd.com;
> > > Mcnamara, John <john.mcnamara@intel.com>; Zhang, Helin
> > > <helin.zhang@intel.com>; techboard@dpdk.org; dev@dpdk.org; Ivan
> Malov
> > > <ivan.malov@arknetworks.am>
> > > Subject: Re: [RFC] lib/ethdev: introduce table driven APIs
> > >
> > > On Mon, Jun 19, 2023 at 5:53 AM Zhang, Qi Z <qi.z.zhang@intel.com>
> wrote:
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Jerin Jacob <jerinjacobk@gmail.com>
> > > > > Sent: Friday, June 16, 2023 9:20 AM
> > > > > To: Zhang, Qi Z <qi.z.zhang@intel.com>; Dumitrescu, Cristian
> > > > > <cristian.dumitrescu@intel.com>
> > > > > Cc: Ori Kam <orika@nvidia.com>; NBU-Contact-Thomas Monjalon
> > > > > (EXTERNAL) <thomas@monjalon.net>; david.marchand@redhat.com;
> > > > > Richardson, Bruce <bruce.richardson@intel.com>; jerinj@marvell.com;
> > > > > ferruh.yigit@amd.com; Mcnamara, John <john.mcnamara@intel.com>;
> > > > > Zhang, Helin <helin.zhang@intel.com>; techboard@dpdk.org;
> > > > > dev@dpdk.org; Ivan Malov <ivan.malov@arknetworks.am>
> > > > > Subject: Re: [RFC] lib/ethdev: introduce table driven APIs
> > > > >
>
> > >
> > > >
> > > > However, the question arises regarding how to handle vendor-specific
> data,
> > > which also can be part of the table / action key and could potentially be
> > > mapped to either rte_flow_item_tag or rte_flow_item_metadata. I'm
> > > uncertain about how the P4-DPDK compiler can manage this aspect.
> Perhaps
> > > this particular aspect should be addressed by each vendor's individual
> > > backend compiler, while we focus on defining the specifications for the
> > > output and providing the common components for parser analysis.
> > >
> > > If we take the compiler path, Why we need vendor specific data?
> >
> > Let's consider the following scenario:
> >
> > Assume that a hardware device contains metadata that can be passed
> between different stages of a pipeline.
> >
> > For instance, in stage A, a rule is matched, and the metadata is set. In stage
> B, this metadata is used as a match key.
> >
> > To design the API calls for the above situation using rte_flow, my
> understanding is that we need to map a rte_flow_item_tag or
> rte_flow_item_metadata to the corresponding metadata portion (including
> offset and size).
> > This way, the driver can understand how to configure the hardware
> accordingly.
> >
> > In P4, we define data structures to abstract the metadata, and the vender
> specific-backend compiler determines the arrangement of the metadata
> space.
> >
> > However, in our case, how does the proposed compiler establish the
> mapping from the P4 metadata key to rte_flow without support from the
> backend compiler?
>
> Yes. We need to change the backend compiler to understand the rte_flow
> mapping to p4 to avoid any translation cost.
+1
I think the idea is that the complier will convert to rte_flow and supply some
mapping file so when application uses some name it will be translated to the correct
preconfigured rte_flow action
next prev parent reply other threads:[~2023-06-20 11:11 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
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 [this message]
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=MW2PR12MB46662EBE06125CBC68F7070DD65CA@MW2PR12MB4666.namprd12.prod.outlook.com \
--to=orika@nvidia.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=jerinjacobk@gmail.com \
--cc=john.mcnamara@intel.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).