On Wed, 6 May 2020 19:48:26 +0000 Liron Himi <[email protected]> wrote:
> Fine. Is there another location or option to save this information? > > Regards, > Liron > > -----Original Message----- > From: Stephen Hemminger <[email protected]> > Sent: Wednesday, 6 May 2020 22:43 > To: Liron Himi <[email protected]> > Cc: dpdk-dev <[email protected]> > Subject: [EXT] Re: [dpdk-dev] input port in mbuf > > External Email > > ---------------------------------------------------------------------- > On Wed, 6 May 2020 19:21:30 +0000 > Liron Himi <[email protected]> wrote: > > > Hi, > > > > We need to save the input port in the mbuf in order to return the buffer to > > the right hw pool. > > For now we use the 'port' in the mbuf as it is supposed to be for this > > exact purpose. > > But we noticed that some applications are override it with the destination > > port. > > > > What should be the right behavior? > > is there another location that that this information can be stored and read > > only by the ethdev drivers? > > > > Regards, > > Liron > > > > There is no requirement that input port is unmodified by the application. The memory pool is already in the mbuf, should go there.
