DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] removal of unused DPDK example apps
Date: Thu, 18 Jul 2019 10:33:14 +0100	[thread overview]
Message-ID: <20190718093314.GB1325@bricha3-MOBL.ger.corp.intel.com> (raw)

A standard item on the agenda of the DPDK technical board meetings has been
the number of example apps in DPDK and whether any of them can be removed.
The board would therefore like to propose that we deprecate a number of
examples in 19.08 and remove them in 19.11.

Here is my initial list of suggested apps to remove, and for a couple of
them the reasons why I consider them for removal.

* exception_path - basically a tun/tap example app, given we have KNI, and
  a tap PMD, this app is probably unneeded.
* l3fwd-vf 
* load_balancer - functionality covered by distributor and eventdev now
* multiprocess/simple_mp - NOTE: not all multi-process apps, just the
  basic, toy one!
* netmap_compat
* quota-watermark
* rxtx_callbacks
* vmdq
* vmdq_dcb

NOTE: Whatever apps are removed will still be available for people to
reference in older releases of DPDK - including our LTS's - as well as in
the git repository, they just won't be available in the latest versions,
and there will no longer be any guarantees that they will compile as DPDK
changes.  The benefits from removing any unwanted apps are that we have
less code to maintain and test, and we have smaller DPDK packages and
faster build times.

At this stage, the technical board is seeking feedback on the proposed
removal of these applications, or if there are other examples that people
feel do not add any value to DPDK and can be removed. All comments welcome.

Regards,
/Bruce

             reply	other threads:[~2019-07-18  9:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18  9:33 Bruce Richardson [this message]
2019-08-09  9:18 ` Tom Barbette

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=20190718093314.GB1325@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --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).