DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-techboard] DPDK techboard minutes of October 24
Date: Mon, 12 Nov 2018 11:24:17 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258010CE495F1@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <fd3172fa-6016-8722-6874-6b6d711976c2@intel.com>


Hi Anatoly,

> > Meeting notes for the DPDK technical board meeting
> > held on 2018-10-24
> >
> > Attendees:
> >          - Bruce Richardson
> >          - Ferruh Yigit
> >          - Hemant Agrawal
> >          - Jerin Jacob
> >          - Konstantin Ananyev
> >          - Maxime Coquelin
> >          - Olivier Matz
> >          - Stephen Hemminger
> >          - Thomas Monjalon
> >
> > 0) DPDK acceptance policy on un-implemented API
> > - New APIs without implementation is not accepted.
> > - In order to accept a new API, At minimum
> > a) Need to provide an unit test case or example application
> > b) If the API is about HW abstraction, at least one driver
> > should be implemented. Preferably two.
> > c) If there are strong objections on ML about the need
> > for more than one driver for a specific API then
> > the technical board can make a decision.
> > - Konstantin volunteered to send existing un-implemented API
> > to the mailing list.
> > - The existing un-implemented APIs will be deprecated in v19.05.
> > - Deprecated un-implemented API will be removed in v19.08
> >
> 
> Does this also apply to unimplemented parts of the existing API? For
> example, malloc API has long had a "name" parameter which goes
> unimplemented through entire lifetime of DPDK project. It would be good
> to drop this thing entirely as it's clear it's not going to be
> implemented any time soon :)
> 

Sounds like a good idea to me.
Konstantin

  reply	other threads:[~2018-11-12 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-10  9:18 [dpdk-dev] " Jerin Jacob
2018-11-12  9:34 ` Burakov, Anatoly
2018-11-12 11:24   ` Ananyev, Konstantin [this message]
2018-11-12 12:21     ` [dpdk-dev] [dpdk-techboard] " Richardson, Bruce
2018-11-12 12:36       ` Ananyev, Konstantin
2018-11-12 16:43         ` Stephen Hemminger
2018-11-12 16:55           ` Thomas Monjalon
2018-11-13  9:33             ` Burakov, Anatoly

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=2601191342CEEE43887BDE71AB977258010CE495F1@IRSMSX106.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=techboard@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).