DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: add ABI change notification for ring library
Date: Tue, 14 Feb 2017 08:55:21 +0530	[thread overview]
Message-ID: <20170214032520.GE3131@localhost.localdomain> (raw)
In-Reply-To: <1487007510-710-1-git-send-email-bruce.richardson@intel.com>

On Mon, Feb 13, 2017 at 05:38:30PM +0000, Bruce Richardson wrote:
> Document proposed changes for the rings code in the next release.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index b49e0a0..e715fc7 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -8,6 +8,25 @@ API and ABI deprecation notices are to be posted here.
>  Deprecation Notices
>  -------------------
>  
> +* ring: Changes are planned to rte_ring APIs in release 17.05. Proposed
> +  changes include:
> +    - Removing build time options for the ring:
> +      CONFIG_RTE_RING_SPLIT_PROD_CONS
> +      CONFIG_RTE_RING_PAUSE_REP_COUNT
> +    - Adding an additional parameter to enqueue functions to return the
> +      amount of free space in the ring
> +    - Adding an additional parameter to dequeue functions to return the
> +      number of remaining elements in the ring
> +    - Removing direct support for watermarks in the rings, since the
> +      additional return value from the enqueue function makes it
> +      unneeded
> +    - Adjusting the return values of the bulk() enq/deq functions to
> +      make them consistent with the burst() equivalents. [Note, parameter
> +      to these functions are changing too, per points above, so compiler
> +      will flag them as needing update in legacy code]
> +    - Updates to some library functions e.g. rte_ring_get_memsize() to
> +      allow for variably-sized ring elements.
> +
>  * igb_uio: iomem mapping and sysfs files created for iomem and ioport in
>    igb_uio will be removed, because we are able to detect these from what Linux
>    has exposed, like the way we have done with uio-pci-generic. This change

Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>

  parent reply	other threads:[~2017-02-14  3:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 17:38 Bruce Richardson
2017-02-14  0:32 ` Mcnamara, John
2017-02-14  3:25 ` Jerin Jacob [this message]
2017-02-14  8:33 ` Olivier Matz
2017-02-14 11:43   ` Hemant Agrawal
2017-02-14 18:42 ` [dpdk-dev] " 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=20170214032520.GE3131@localhost.localdomain \
    --to=jerin.jacob@caviumnetworks.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 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).