From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, "Richardson, Bruce" <bruce.richardson@intel.com>,
"Wiles, Keith" <keith.wiles@intel.com>
Subject: Re: [dpdk-dev] doc: deprecation notice for ethdev ops?
Date: Mon, 13 Feb 2017 18:39:25 +0100 [thread overview]
Message-ID: <53116045.9rx8z4L4Mf@xps13> (raw)
In-Reply-To: <894e4d0b-9541-c374-eabb-a1e0320e7347@intel.com>
2017-02-13 17:36, Ferruh Yigit:
> On 2/13/2017 5:21 PM, Dumitrescu, Cristian wrote:
> > Do you have a specific example that might cause an issue when adding a new function at the end of the ethdev ops structure? I cannot think of any, given that the ops structure is marked as internal and it is only accessed through pointers.
>
> Adding at the end of the struct is probably safe.
There is no guarantee in DPDK for drivers interface compatibility.
You can add your op anywhere relevant in the structure.
next prev parent reply other threads:[~2017-02-13 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 16:02 Dumitrescu, Cristian
2017-02-13 16:09 ` Thomas Monjalon
2017-02-13 16:46 ` Ferruh Yigit
2017-02-13 17:21 ` Dumitrescu, Cristian
2017-02-13 17:36 ` Ferruh Yigit
2017-02-13 17:39 ` Thomas Monjalon [this message]
2017-02-13 17:38 ` Thomas Monjalon
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=53116045.9rx8z4L4Mf@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=keith.wiles@intel.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).