From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org, Gage Eads <gage.eads@intel.com>
Cc: olivier.matz@6wind.com, arybchenko@solarflare.com,
bruce.richardson@intel.com, konstantin.ananyev@intel.com,
stephen@networkplumber.org, john.mcnamara@intel.com
Subject: Re: [PATCH v3] doc: announce ring API change
Date: Fri, 01 Feb 2019 12:16:41 +0100 [thread overview]
Message-ID: <172114315.O9AQeyJeYo@xps> (raw)
In-Reply-To: <20190118153117.23810-1-gage.eads@intel.com>
18/01/2019 16:31, Gage Eads:
> In order to support the non-blocking ring[1], an API change (additional
> argument to rte_ring_get_memsize()) is required in librte_ring. This commit
> updates the deprecation notice to pave the way for its inclusion in
> 19.05.
>
> [1] http://mails.dpdk.org/archives/dev/2019-January/123774.html
>
> Signed-off-by: Gage Eads <gage.eads@intel.com>
Nobody agreed on this change.
Gage, do you still want to push non-blocking ring in 19.05?
---
> +* ring: one change is planned for rte_ring in v19.05:
> +
> + - rte_ring_get_memsize() will get a new ``flags`` parameter, so it can
> + calculate the memory required for rings that require more than 8B per entry
> + (such as the upcoming non-blocking ring).
next prev parent reply other threads:[~2019-02-01 11:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 23:59 [PATCH] doc: announce ring ABI and API changes Gage Eads
2019-01-16 0:34 ` Stephen Hemminger
2019-01-16 18:21 ` Eads, Gage
2019-01-18 15:28 ` [PATCH v2] doc: announce ring API change Gage Eads
2019-01-18 15:31 ` [PATCH v3] " Gage Eads
2019-02-01 11:16 ` Thomas Monjalon [this message]
2019-02-01 14:18 ` Eads, Gage
2019-02-01 14:36 ` [PATCH v4] " Gage Eads
2019-05-09 23:29 ` [dpdk-dev] " Thomas Monjalon
2019-05-10 14:53 ` Eads, Gage
2019-05-10 14:58 ` Stephen Hemminger
2019-05-10 15:19 ` Ola Liljedahl
2019-05-10 16:28 ` Eads, Gage
2019-05-13 11:46 ` Olivier Matz
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=172114315.O9AQeyJeYo@xps \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.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.