DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Liron Himi <lironh@marvell.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Re:  input port in mbuf
Date: Wed, 6 May 2020 22:10:01 +0000
Message-ID: <BYAPR11MB3301C5B893797FDD3431007A9AA40@BYAPR11MB3301.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM5PR18MB22149AC1AEFFA6569DCB597DC6A40@DM5PR18MB2214.namprd18.prod.outlook.com>

> For performance optimizations, we need to know the input DPDK port as after the buffer was transmitted via our ethdev driver instead of
> release it back to the memory-pool we can release it to the originated HW pool of the input port.

Then I suppose, you can have your own mempool driver,
and do whatever you like there.

> 
> 
> Regards,
> Liron
> 
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Wednesday, 6 May 2020 23:11
> To: Liron Himi <lironh@marvell.com>
> Cc: dpdk-dev <dev@dpdk.org>
> Subject: Re: [EXT] Re: [dpdk-dev] input port in mbuf
> 
> On Wed, 6 May 2020 19:48:26 +0000
> Liron Himi <lironh@marvell.com> wrote:
> 
> > Fine. Is there another location or option to save this information?
> >
> > Regards,
> > Liron
> >
> > -----Original Message-----
> > From: Stephen Hemminger <stephen@networkplumber.org>
> > Sent: Wednesday, 6 May 2020 22:43
> > To: Liron Himi <lironh@marvell.com>
> > Cc: dpdk-dev <dev@dpdk.org>
> > Subject: [EXT] Re: [dpdk-dev] input port in mbuf
> >
> > External Email
> >
> > ----------------------------------------------------------------------
> > On Wed, 6 May 2020 19:21:30 +0000
> > Liron Himi <lironh@marvell.com> 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.

      parent reply	other threads:[~2020-05-06 22:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 19:21 [dpdk-dev] " Liron Himi
2020-05-06 19:42 ` Stephen Hemminger
2020-05-06 19:48   ` [dpdk-dev] [EXT] " Liron Himi
2020-05-06 20:10     ` Stephen Hemminger
2020-05-06 20:17       ` Liron Himi
2020-05-06 20:23         ` Stephen Hemminger
2021-01-16 20:01           ` Liron Himi
2021-01-27 16:58             ` Tom Barbette
2021-01-27 17:59               ` Liron Himi
2020-05-06 22:10         ` Ananyev, Konstantin [this message]

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=BYAPR11MB3301C5B893797FDD3431007A9AA40@BYAPR11MB3301.namprd11.prod.outlook.com \
    --to=konstantin.ananyev@intel.com \
    --cc=dev@dpdk.org \
    --cc=lironh@marvell.com \
    --cc=stephen@networkplumber.org \
    /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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git