From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: dev@dpdk.org
Cc: hemant.agrawal@nxp.com, thomas@monjalon.net
Subject: [dpdk-dev] NXP's DPDK Roadmap for 18.05
Date: Tue, 27 Feb 2018 15:15:48 +0530 [thread overview]
Message-ID: <fed0ab99-1b7f-66e3-9558-b870b94d5f9d@nxp.com> (raw)
Following are some of the key work items which we are planning for DPDK
1805:
1. Two rawdevice drivers
- for communication interface to interact with a specialized block
(AIOP: Advanced I/O Processor) on dpaa2.
- and, for DMA accelerator support on dpaa2 devices to userspace
2. Crypto adapter for eventdev for dpaa1/dpaa2.
- This directly dependent on the crypto adapter base code [1] getting
finalized within the window.
3. Change to rte_eth_dev_info for supporting driver advertised burst
size as described in deprecation notice [2].
- this would enable applications to tune their bursts according to the
driver's preferred size, allowing a knob to tune into higher device
specific performance.
4. Meson support
- this includes dpaa1/dpaa2 components (bus/mempool/net/crypto/event)
- and for lib_rawdev
5. Integrating dpaa1/dpaa2 compilation into common_linuxapp
configuration to allow dpaa1/dpaa2 compilation as default objects along
with other PMDs.
6. A new ethernet driver for ENETC (using PCI bus) for NXP LS1028 SoC.
Various other trivial activities include:
-) Dynamic Logging for dpaa2 and some changes for dpaa1 as well for
cleaning up logs.
-) Device whitelist/blacklist support for dpaa1/dpaa2 devices. This is
dependent on the devargs work being done. [2]
-) Ethdev offload API support
-) coverity reported fixes
Flow director support for dpaa2 is also on the cards, but probably that
would be targeted only on best-effort basis.
===
[1] http://dpdk.org/ml/archives/dev/2018-February/090807.html - RFC for
crypto adapter for event devices
[2] http://dpdk.org/ml/archives/dev/2018-February/090157.html -
deprecation notice for burst size change
-
Shreyansh
reply other threads:[~2018-02-27 9:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fed0ab99-1b7f-66e3-9558-b870b94d5f9d@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).