> -----Original Message-----
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Tuesday, December 18, 2018 12:38 PM
> To: Dumitrescu, Cristian <cristian.dumitre...@intel.com>
> Cc: Pattan, Reshma <reshma.pat...@intel.com>; dev@dpdk.org; Ananyev,
> Konstantin <konstantin.anan...@intel.com>;
> jerin.ja...@caviumnetworks.com; Singh, Jasvinder
> <jasvinder.si...@intel.com>; david.march...@redhat.com;
> olivier.m...@6wind.com
> Subject: Re: [dpdk-dev] [PATCH v2 2/3] eal: add new rte color definition
>
> 18/12/2018 12:18, Dumitrescu, Cristian:
> > > > I replied in v3 that it should stay in rte_meter.h.
> > > > You can include rte_meter.h in ethdev.
> > >
> > > OK, thanks Thomas, makes sense to me as well.
> > >
> >
> > Thomas,
> >
> > I agree with your input, but just want to make sure we are on the same
> page:
> >
> > Besides including rte_meter.h in ethdev (which you are fine with), we
> would also need to include rte_meter.h in mbuf.
> >
> > Are you OK with this as well?
>
> Why do we need rte_meter.h in mbuf?
>
You probably looked at V2 only, but in V3 we have functions to set/get the
color within the mbuf->hash.sched field.
For space compression reasons, the mbuf->hash.sched stores the color on 8-bit
variable, while for the outside world the set/get functions work with the
32-bit enum type. We do same thing in other places in DPDK, such as
rte_crypto_op, etc.
