From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
Cc: dev@dpdk.org, "Olivier Matz" <olivier.matz@6wind.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Wiles, Keith" <keith.wiles@intel.com>
Subject: Re: [dpdk-dev] mbuf changes
Date: Tue, 25 Oct 2016 16:54:29 +0200 [thread overview]
Message-ID: <2356525.jla7534a8z@xps13> (raw)
In-Reply-To: <682698A055A0F44AA47192B2014114976258DC35@BGSMSX102.gar.corp.intel.com>
2016-10-25 14:32, Ramia, Kannan Babu:
> I didn't get your question. The only information exchanged between the stages is mbuf pointer. So the information has to be in mbuf, whether it's part of Meta or in private area in the packet buffer headroom is that the question you are asking. The private area is application specific, while I am looking for the port information getting updated from driver to application and it's generic to multiple applications.
Thanks, your answer is perfect (except it is top-posted ;)
The discussion is more about performance. So you agree that the port
information is not performance sensitive.
It appears that it could be an information filled in a private area
at app-level, because the application knows which port it is polling.
However we may need a way to put some generic informations somewhere,
not in the first cache lines.
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, October 25, 2016 6:54 PM
> To: Ramia, Kannan Babu <kannan.babu.ramia@intel.com>
> Cc: dev@dpdk.org; Olivier Matz <olivier.matz@6wind.com>; Morten Brørup <mb@smartsharesystems.com>; Ananyev, Konstantin <konstantin.ananyev@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>; Wiles, Keith <keith.wiles@intel.com>
> Subject: Re: [dpdk-dev] mbuf changes
>
> 2016-10-25 13:04, Ramia, Kannan Babu:
> > Port filed is important meta information for the application use like
> > CGNAT vEPC functions etc.
> > I strongly recommend to keep the field in mind meta.
>
> Have you tried to move this field outside of the mbuf?
> What is the performance degradation?
> We need more information than some assumptions.
>
next prev parent reply other threads:[~2016-10-25 14:54 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 15:49 Morten Brørup
2016-10-24 16:11 ` Wiles, Keith
2016-10-24 16:25 ` Bruce Richardson
2016-10-24 21:47 ` Morten Brørup
2016-10-25 8:53 ` Bruce Richardson
2016-10-25 10:02 ` Ananyev, Konstantin
2016-10-25 10:22 ` Morten Brørup
2016-10-25 13:00 ` Olivier Matz
2016-10-25 13:04 ` Ramia, Kannan Babu
2016-10-25 13:24 ` Thomas Monjalon
2016-10-25 14:32 ` Ramia, Kannan Babu
2016-10-25 14:54 ` Thomas Monjalon [this message]
2016-10-25 13:15 ` Bruce Richardson
2016-10-25 13:20 ` Thomas Monjalon
2016-10-25 9:39 ` Adrien Mazarguil
2016-10-25 10:11 ` Morten Brørup
2016-10-25 11:04 ` Adrien Mazarguil
2016-10-25 11:13 ` Bruce Richardson
2016-10-25 12:16 ` Morten Brørup
2016-10-25 12:20 ` Bruce Richardson
2016-10-25 12:33 ` Morten Brørup
2016-10-25 12:45 ` Bruce Richardson
2016-10-25 12:48 ` Olivier Matz
2016-10-25 13:13 ` Morten Brørup
2016-10-25 13:38 ` Ananyev, Konstantin
2016-10-25 14:25 ` Morten Brørup
2016-10-25 14:45 ` Olivier Matz
2016-10-28 13:34 ` Pattan, Reshma
2016-10-28 14:11 ` Morten Brørup
2016-10-28 15:25 ` Pattan, Reshma
2016-10-28 16:50 ` Adrien Mazarguil
2016-10-28 17:00 ` Richardson, Bruce
2016-10-28 20:27 ` Morten Brørup
2016-10-31 10:55 ` Morten Brørup
2016-10-31 16:05 ` Morten Brørup
2016-10-25 13:48 ` Adrien Mazarguil
2016-10-25 13:58 ` Ananyev, Konstantin
2016-10-25 11:54 ` Shreyansh Jain
2016-10-25 12:05 ` Bruce Richardson
2016-10-26 8:28 ` Alejandro Lucero
2016-10-26 9:01 ` Morten Brørup
2016-11-09 11:42 ` Alejandro Lucero
2016-11-10 9:19 ` [dpdk-dev] Fwd: " Alejandro Lucero
2016-10-25 12:49 ` [dpdk-dev] " Morten Brørup
2016-10-25 13:14 ` Olivier Matz
2016-10-25 13:18 ` Morten Brørup
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=2356525.jla7534a8z@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=kannan.babu.ramia@intel.com \
--cc=keith.wiles@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=mb@smartsharesystems.com \
--cc=olivier.matz@6wind.com \
/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).