From: Amr Mokhtar <amr.mokhtar@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, ferruh.yigit@intel.com,
anatoly.burakov@intel.com, pablo.de.lara.guarch@intel.com,
niall.power@intel.com, chris.macnamara@intel.com,
Amr Mokhtar <amr.mokhtar@intel.com>
Subject: [dpdk-dev] [PATCH v4 0/5] Introducing Wirless Base Band Device (bbdev) abstraction library
Date: Sat, 23 Dec 2017 00:52:11 +0000 [thread overview]
Message-ID: <1513990331-20253-6-git-send-email-amr.mokhtar@intel.com> (raw)
In-Reply-To: <1513990331-20253-1-git-send-email-amr.mokhtar@intel.com>
Hello,
An updated v4 patch of the Wireless Baseband Device (bbdev) abstraction
library is enclosed. Addressing the feedback received from the
community on the application interface in the RFC, v1 and v3 patches.
v4:
* Organized patch set
* Enhanced bbdev sample app
* Turbo operation application interface is better documented
v3:
* Cleaner Turbo Code operation interface
* Enahnced SW Turbo PMD (turbo_sw)
* Removed pci & vdev dependency from bbdev library interface
* Updated download instructions for Intel FlexRAN SDK library
http://dpdk.org/dev/patchwork/patch/31990/
http://dpdk.org/dev/patchwork/patch/31991/
http://dpdk.org/dev/patchwork/patch/31992/
http://dpdk.org/dev/patchwork/patch/31993/
http://dpdk.org/dev/patchwork/patch/31994/
v2:
* Split the functionality of rte_bbdev_configure() into smaller portions ->
rte_bbdev_setup_queues() and rte_bbdev_enale_intr()
* Split rte_bbdev_enqueue() -> rte_bbdev_enc_enqueue() and rte_bbdev_dec_enqueue()
* Split rte_bbdev_dequeue() -> rte_bbdev_enc_dequeue() and rte_bbdev_dec_dequeue()
* Removed attached flag until hotplug is properly supported in DPDK
* More details on the installation of FlexRAN SDK libraries in accordance with Turbo_sw PMD
* Minor build fixes for other targets: bsdapp-gcc, bsdapp-clang and linuxapp-clang.
* Better-organized patchwork
http://dpdk.org/dev/patchwork/patch/30498/
http://dpdk.org/dev/patchwork/patch/30499/
http://dpdk.org/dev/patchwork/patch/30500/
http://dpdk.org/dev/patchwork/patch/30501/
http://dpdk.org/dev/patchwork/patch/30502/
v1:
* Initial release of BBDEV library.
* Support Turbo Code FEC with two virtual devices (vdev):
- Null Turbo PMD
- Turbo_sw PMD
* A complete Test suite for Turbo Encode/Decode and None operations
* Test Vectors parsing and testing functionality
* Sample App for a looped-back bbdev with ethdev
* Documentation in rst format for all new components
http://dpdk.org/dev/patchwork/patch/29447/
http://dpdk.org/dev/patchwork/patch/29448/
http://dpdk.org/dev/patchwork/patch/29450/
http://dpdk.org/dev/patchwork/patch/29449/
http://dpdk.org/dev/patchwork/patch/29452/
http://dpdk.org/dev/patchwork/patch/29451/
RFC:
http://dpdk.org/dev/patchwork/patch/27984/
Amr Mokhtar (5):
bbdev: introducing wireless base band device (BBDEV) abstraction
library
bbdev: PMD drivers (1. bbdev_null)
bbdev: PMD drivers (2. turbo_sw)
bbdev: test applications
bbdev: sample app
MAINTAINERS | 11 +
app/Makefile | 4 +
app/test-bbdev/Makefile | 22 +
app/test-bbdev/main.c | 325 +++
app/test-bbdev/main.h | 120 ++
app/test-bbdev/test-bbdev.py | 111 +
app/test-bbdev/test_bbdev.c | 1378 ++++++++++++
app/test-bbdev/test_bbdev_perf.c | 2186 ++++++++++++++++++++
app/test-bbdev/test_bbdev_vector.c | 937 +++++++++
app/test-bbdev/test_bbdev_vector.h | 71 +
app/test-bbdev/test_vectors/bbdev_vector_null.data | 5 +
.../test_vectors/bbdev_vector_td_default.data | 54 +
.../test_vectors/bbdev_vector_te_default.data | 33 +
config/common_base | 22 +
doc/api/doxy-api-index.md | 1 +
doc/api/doxy-api.conf | 1 +
doc/guides/bbdevs/index.rst | 13 +
doc/guides/bbdevs/null.rst | 50 +
doc/guides/bbdevs/turbo_sw.rst | 148 ++
doc/guides/index.rst | 1 +
doc/guides/prog_guide/bbdev.rst | 586 ++++++
doc/guides/prog_guide/index.rst | 1 +
doc/guides/rel_notes/release_18_02.rst | 12 +
doc/guides/sample_app_ug/bbdev_app.rst | 133 ++
doc/guides/sample_app_ug/index.rst | 1 +
doc/guides/tools/index.rst | 1 +
doc/guides/tools/testbbdev.rst | 573 +++++
drivers/Makefile | 2 +
drivers/bbdev/Makefile | 14 +
drivers/bbdev/null/Makefile | 24 +
drivers/bbdev/null/bbdev_null.c | 346 ++++
drivers/bbdev/null/rte_pmd_bbdev_null_version.map | 3 +
drivers/bbdev/turbo_sw/Makefile | 41 +
drivers/bbdev/turbo_sw/bbdev_turbo_software.c | 1206 +++++++++++
.../turbo_sw/rte_pmd_bbdev_turbo_sw_version.map | 3 +
examples/Makefile | 1 +
examples/bbdev_app/Makefile | 22 +
examples/bbdev_app/main.c | 1146 ++++++++++
lib/Makefile | 2 +
lib/librte_bbdev/Makefile | 28 +
lib/librte_bbdev/rte_bbdev.c | 1115 ++++++++++
lib/librte_bbdev/rte_bbdev.h | 714 +++++++
lib/librte_bbdev/rte_bbdev_op.h | 638 ++++++
lib/librte_bbdev/rte_bbdev_pmd.h | 195 ++
lib/librte_bbdev/rte_bbdev_version.map | 37 +
mk/rte.app.mk | 13 +
46 files changed, 12350 insertions(+)
create mode 100644 app/test-bbdev/Makefile
create mode 100644 app/test-bbdev/main.c
create mode 100644 app/test-bbdev/main.h
create mode 100755 app/test-bbdev/test-bbdev.py
create mode 100644 app/test-bbdev/test_bbdev.c
create mode 100644 app/test-bbdev/test_bbdev_perf.c
create mode 100644 app/test-bbdev/test_bbdev_vector.c
create mode 100644 app/test-bbdev/test_bbdev_vector.h
create mode 100644 app/test-bbdev/test_vectors/bbdev_vector_null.data
create mode 100644 app/test-bbdev/test_vectors/bbdev_vector_td_default.data
create mode 100644 app/test-bbdev/test_vectors/bbdev_vector_te_default.data
create mode 100644 doc/guides/bbdevs/index.rst
create mode 100644 doc/guides/bbdevs/null.rst
create mode 100644 doc/guides/bbdevs/turbo_sw.rst
create mode 100644 doc/guides/prog_guide/bbdev.rst
create mode 100644 doc/guides/sample_app_ug/bbdev_app.rst
create mode 100644 doc/guides/tools/testbbdev.rst
create mode 100644 drivers/bbdev/Makefile
create mode 100644 drivers/bbdev/null/Makefile
create mode 100644 drivers/bbdev/null/bbdev_null.c
create mode 100644 drivers/bbdev/null/rte_pmd_bbdev_null_version.map
create mode 100644 drivers/bbdev/turbo_sw/Makefile
create mode 100644 drivers/bbdev/turbo_sw/bbdev_turbo_software.c
create mode 100644 drivers/bbdev/turbo_sw/rte_pmd_bbdev_turbo_sw_version.map
create mode 100644 examples/bbdev_app/Makefile
create mode 100644 examples/bbdev_app/main.c
create mode 100644 lib/librte_bbdev/Makefile
create mode 100644 lib/librte_bbdev/rte_bbdev.c
create mode 100644 lib/librte_bbdev/rte_bbdev.h
create mode 100644 lib/librte_bbdev/rte_bbdev_op.h
create mode 100644 lib/librte_bbdev/rte_bbdev_pmd.h
create mode 100644 lib/librte_bbdev/rte_bbdev_version.map
--
2.7.4
next prev parent reply other threads:[~2017-12-23 0:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 0:52 [dpdk-dev] [PATCH v4 1/5] bbdev: introducing wireless base band device (BBDEV) " Amr Mokhtar
2017-12-23 0:52 ` [dpdk-dev] [PATCH v4 2/5] bbdev: PMD drivers (1. bbdev_null) Amr Mokhtar
2018-01-09 19:18 ` Ferruh Yigit
2017-12-23 0:52 ` [dpdk-dev] [PATCH v4 3/5] bbdev: PMD drivers (2. turbo_sw) Amr Mokhtar
2018-01-09 19:18 ` Ferruh Yigit
2017-12-23 0:52 ` [dpdk-dev] [PATCH v4 4/5] bbdev: test applications Amr Mokhtar
2018-01-09 19:27 ` Ferruh Yigit
2017-12-23 0:52 ` [dpdk-dev] [PATCH v4 5/5] bbdev: sample app Amr Mokhtar
2017-12-23 0:52 ` Amr Mokhtar [this message]
2018-01-09 19:17 ` [dpdk-dev] [PATCH v4 1/5] bbdev: introducing wireless base band device (BBDEV) abstraction library Ferruh Yigit
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=1513990331-20253-6-git-send-email-amr.mokhtar@intel.com \
--to=amr.mokhtar@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=chris.macnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=niall.power@intel.com \
--cc=pablo.de.lara.guarch@intel.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 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).