DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 01/10] table: added structure for storing table stats
Date: Thu, 28 May 2015 14:41:17 -0700	[thread overview]
Message-ID: <20150528144117.4d58fada@urahara> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891263236E6E6@IRSMSX108.ger.corp.intel.com>

On Thu, 28 May 2015 19:32:32 +0000
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com> wrote:

> This is just adding  a new field at the end of an API data structure. Based on input from multiple people and after reviewing the rules listed on http://dpdk.org/doc/guides/rel_notes/abi.html , I think this is an acceptable change. There are other patches in flight on this mailing list that are in the same situation. Any typical/well behaved application will not break due to this change.

Expanding a structure can be okay but:
  1. The allocation will have to always take within the library.
     If you let application put structure on stack or allocate on it's own, the ABI would break.

  2. The structure must not be used as a return by reference.
     For example, this would break if sizeof(struct my_stats) changed.

     void foo() {
             struct my_stats stats;
	     int i_will_get_clobbered;
	...
		rte_dpdk_get_stats(obj, &stats)
	}

  reply	other threads:[~2015-05-28 21:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 12:39 [dpdk-dev] [PATCH v3 00/10] table: added table statistics Maciej Gajdzica
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 01/10] table: added structure for storing table stats Maciej Gajdzica
2015-05-26 14:57   ` Stephen Hemminger
2015-05-26 21:40     ` Dumitrescu, Cristian
2015-05-26 21:57       ` Stephen Hemminger
2015-05-28 19:32         ` Dumitrescu, Cristian
2015-05-28 21:41           ` Stephen Hemminger [this message]
2015-05-26 22:03   ` Chris Wright
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 02/10] table: added acl " Maciej Gajdzica
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 03/10] table: added array " Maciej Gajdzica
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 04/10] table: added hash_ext " Maciej Gajdzica
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 05/10] table: added hash_key16 " Maciej Gajdzica
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 06/10] table: added hash_key32 " Maciej Gajdzica
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 07/10] table: added hash_key8 " Maciej Gajdzica
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 08/10] table: added hash_lru " Maciej Gajdzica
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 09/10] table: added lpm_ipv6 " Maciej Gajdzica
2015-05-26 12:39 ` [dpdk-dev] [PATCH v3 10/10] table: added lpm " Maciej Gajdzica
2015-05-26 13:39 ` [dpdk-dev] [PATCH v3 00/10] table: added table statistics Dumitrescu, Cristian

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=20150528144117.4d58fada@urahara \
    --to=stephen@networkplumber.org \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.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).