From: Matthew Hall <mhall@mhcomputing.net>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] difficulty w/ RTE_NEXT_ABI
Date: Sat, 21 Nov 2015 19:25:18 -0500 [thread overview]
Message-ID: <20151122002518.GA7196@mhcomputing.net> (raw)
In-Reply-To: <2295250.tyqBLnBnCL@xps13>
On Sat, Nov 21, 2015 at 11:44:20AM +0100, Thomas Monjalon wrote:
> The new mbuf provides packet type instead of flags.
> So the processing in this function is changed and the variable name is
> different to reflect this.
But the data type of the variable is the same, and this is an internal
always_inline function.
So again I am confused what advantage we got from RTE_NEXT_ABI here, and how
you have multiple copies of RTE_NEXT_ABI on a single symbol when it is a
binary variable.
This doesn't really answer the bigger question about the reasoning.
Matthew.
next prev parent reply other threads:[~2015-11-22 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 8:49 Matthew Hall
2015-11-21 10:44 ` Thomas Monjalon
2015-11-22 0:25 ` Matthew Hall [this message]
2015-11-22 20:59 ` Thomas Monjalon
2015-11-22 23:25 ` Matthew Hall
2015-11-23 0:13 ` Thomas Monjalon
2015-11-23 3:53 ` Matthew Hall
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=20151122002518.GA7196@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@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).