All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 7/7] abi: announce mbuf addition for ieee1588 in DPDK 2.2
Date: Thu, 09 Jul 2015 17:51:16 +0200	[thread overview]
Message-ID: <2534416.XSNtN7mPxB@xps13> (raw)
In-Reply-To: <20150708131034.GA5708@bricha3-MOBL3>

2015-07-08 14:10, Bruce Richardson:
> On Mon, Jul 06, 2015 at 03:16:01PM +0200, Thomas Monjalon wrote:
> > 2015-07-02 16:16, John McNamara:
> > > --- a/doc/guides/rel_notes/abi.rst
> > > +++ b/doc/guides/rel_notes/abi.rst
> > >  Deprecation Notices
> > >  -------------------
> > > +
> > > +* In DPDK 2.1 the IEEE1588/802.1AS support in the i40e driver makes use of the
> > > +  ``udata64`` field in the mbuf to pass the timesync register index to the
> > > +  user. In DPDK 2.2 this will be moved to a new field in the mbuf.
> > 
> > We need more acknowledgements for this decision, as stated here:
> > http://dpdk.org/browse/dpdk/tree/doc/guides/guidelines/versioning.rst#n51
> 
> Why can't this new field just be added at the end of cache line 1 (the second
> cache line) of the mbuf? That would avoid any ABI breakage and would mean we
> can just put the change in in this release, instead of waiting.

Are you sure that (because of __rte_cache_aligned) the size of the structure
is never increased with this new field?
Please confirm your opinion.

A comment to explain ABI compatibility in the commit message of the v4 is
also welcome.

  reply	other threads:[~2015-07-09 15:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 13:42 [PATCH v2 0/7] ethdev: add support for ieee1588 timestamping John McNamara
2015-06-29 13:42 ` [PATCH v2 1/7] " John McNamara
2015-07-02 10:17   ` Thomas Monjalon
2015-07-02 15:14     ` Mcnamara, John
2015-06-29 13:42 ` [PATCH v2 2/7] e1000: " John McNamara
2015-06-29 13:42 ` [PATCH v2 3/7] ixgbe: " John McNamara
2015-06-29 13:42 ` [PATCH v2 4/7] i40e: " John McNamara
2015-06-29 13:42 ` [PATCH v2 5/7] app/testpmd: refactor ieee1588 forwarding John McNamara
2015-06-29 13:42 ` [PATCH v2 6/7] doc: document ieee1588 forwarding mode John McNamara
2015-06-29 13:42 ` [PATCH v2 7/7] abi: announce mbuf addition for ieee1588 in DPDK 2.2 John McNamara
2015-07-02  1:24 ` [PATCH v2 0/7] ethdev: add support for ieee1588 timestamping Lu, Wenzhuo
2015-07-02 15:16 ` [PATCH v3 " John McNamara
2015-07-02 15:16   ` [PATCH v3 1/7] " John McNamara
2015-07-02 15:16   ` [PATCH v3 2/7] e1000: " John McNamara
2015-07-02 15:16   ` [PATCH v3 3/7] ixgbe: " John McNamara
2015-07-02 15:16   ` [PATCH v3 4/7] i40e: " John McNamara
2015-07-02 15:16   ` [PATCH v3 5/7] app/testpmd: refactor ieee1588 forwarding John McNamara
2015-07-02 15:16   ` [PATCH v3 6/7] doc: document ieee1588 forwarding mode John McNamara
2015-07-02 15:16   ` [PATCH v3 7/7] abi: announce mbuf addition for ieee1588 in DPDK 2.2 John McNamara
2015-07-06 13:16     ` Thomas Monjalon
2015-07-08 13:10       ` Bruce Richardson
2015-07-09 15:51         ` Thomas Monjalon [this message]
2015-07-09 16:01           ` Bruce Richardson
2015-07-03  8:22   ` [PATCH v3 0/7] ethdev: add support for ieee1588 timestamping Lu, Wenzhuo
2015-07-08  1:59   ` Fu, JingguoX

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=2534416.XSNtN7mPxB@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.