From: Liron Himi <lironh@marvell.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dpdk-dev <dev@dpdk.org>, Liron Himi <lironh@marvell.com>
Subject: Re: [dpdk-dev] [EXT] Re: input port in mbuf
Date: Wed, 6 May 2020 19:48:26 +0000 [thread overview]
Message-ID: <DM5PR18MB22143F34E1B5946343E6A216C6A40@DM5PR18MB2214.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20200506124258.69b138e4@hermes.lan>
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.
next prev parent reply other threads:[~2020-05-06 19:48 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 ` Liron Himi [this message]
2020-05-06 20:10 ` [dpdk-dev] [EXT] " 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
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=DM5PR18MB22143F34E1B5946343E6A216C6A40@DM5PR18MB2214.namprd18.prod.outlook.com \
--to=lironh@marvell.com \
--cc=dev@dpdk.org \
--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
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).