From: Stephen Hemminger <stephen@networkplumber.org>
To: "Eads, Gage" <gage.eads@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>,
"gavin.hu@arm.com" <gavin.hu@arm.com>,
"Ola.Liljedahl@arm.com" <Ola.Liljedahl@arm.com>,
"nd@arm.com" <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v4] doc: announce ring API change
Date: Fri, 10 May 2019 07:58:55 -0700 [thread overview]
Message-ID: <20190510075855.2899716e@hermes.lan> (raw)
In-Reply-To: <9184057F7FC11744A2107296B6B8EB1E68CB470E@fmsmsx101.amr.corp.intel.com>
On Fri, 10 May 2019 14:53:56 +0000
"Eads, Gage" <gage.eads@intel.com> wrote:
> > 01/02/2019 15:36, 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.08.
> > >
> > > [1] http://mails.dpdk.org/archives/dev/2019-January/124162.html
> > >
> > > Signed-off-by: Gage Eads <gage.eads@intel.com>
> >
> > There is still no agreement on this change?
> >
>
> Still none. I was hoping this discussion (http://mails.dpdk.org/archives/dev/2019-April/129229.html) would lead to some clear direction, but at this point the effort is stalled.
The fundamental tradeoff is between non-blocking rings and ABI breakage.
Why not have a new ring type for non-blocking rings since non-blocking
rings are not necessary for all use cases.
next prev parent reply other threads:[~2019-05-10 14:59 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
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 [this message]
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=20190510075855.2899716e@hermes.lan \
--to=stephen@networkplumber.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ola.Liljedahl@arm.com \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=gavin.hu@arm.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.com \
--cc=thomas@monjalon.net \
/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.