Hi,

> -----Original Message-----
> From: Ori Kam <[email protected]>
> Sent: Wednesday, October 6, 2021 9:10 AM
> To: Somnath Kotur <[email protected]>; Ajit Khaparde
> <[email protected]>
> Cc: Ivan Malov <[email protected]>; dpdk-dev <[email protected]>; Ray
> Kinsella <[email protected]>; Jerin Jacob <[email protected]>; NBU-Contact-
> Thomas Monjalon <[email protected]>; Andrew Rybchenko
> <[email protected]>; Andy Moreton
> <[email protected]>; Wisam Monther <[email protected]>; Xiaoyun
> Li <[email protected]>; Ferruh Yigit <[email protected]>
> Subject: RE: [dpdk-dev] [PATCH v5 1/5] ethdev: negotiate delivery of packet
> metadata from HW to PMD
> 
> Hi Ivan,
> 
> > -----Original Message-----
> > From: Somnath Kotur <[email protected]>
> > Sent: Wednesday, October 6, 2021 9:04 AM metadata from HW to PMD
> >
> > On Wed, Oct 6, 2021 at 3:10 AM Ajit Khaparde
> > <[email protected]> wrote:
> > >
> > > On Tue, Oct 5, 2021 at 8:56 AM Ivan Malov <[email protected]>
> > wrote:
> > > >
> > > > Provide an API to let the application control the NIC's ability to
> > > > deliver specific kinds of per-packet metadata to the PMD.
> > > >
> > > > Checks for the NIC's ability to set these kinds of metadata in the
> > > > first place (support for the flow actions) belong in flow API
> > > > responsibility domain (flow validate mechanism).
> > > > This topic is out of scope of the new API in question.
> > > >
> > > > The PMD's ability to deliver received metadata to the user by
> > > > virtue of mbuf fields should be covered by mbuf library.
> > > > It is also out of scope of the new API in question.
> > > >
> > > > Signed-off-by: Ivan Malov <[email protected]>
> > > > Reviewed-by: Andrew Rybchenko <[email protected]>
> > > > Reviewed-by: Andy Moreton <[email protected]>
> > > > Acked-by: Ray Kinsella <[email protected]>
> > > > Acked-by: Jerin Jacob <[email protected]>
> > >
> > > Acked-by: Ajit Khaparde <[email protected]>
> > Acked-by: Somnath Kotur <[email protected]>
> Acked-by: Ori Kam <[email protected]>

Acked-by: Wisam Jaddo <[email protected]>


BRs,
Wisam Jaddo

Reply via email to