From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: 'dpdk-dev' <dev@dpdk.org>
Cc: Prasun Kapoor <pkapoor@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Narayana Prasad Raju Athreya <pathreya@marvell.com>,
Dovrat Zifroni <dovrat@marvell.com>,
Nagadheeraj Rottela <rnagadheeraj@marvell.com>,
Srikanth Jampala <jsrikanth@marvell.com>,
Ameen Rahman <arahman@marvell.com>,
Rasesh Mody <rmody@marvell.com>,
Shahed Shaikh <shshaikh@marvell.com>,
GR-Ipbu-sw-dpdk <GR-Ipbu-sw-dpdk@marvell.com>
Subject: [dpdk-dev] Marvell DPDK 20.05 Roadmap
Date: Thu, 27 Feb 2020 07:49:41 +0000 [thread overview]
Message-ID: <BN8PR18MB24174D92B420FEFD5B228A17C8EB0@BN8PR18MB2417.namprd18.prod.outlook.com> (raw)
General:
--------
# Add High-performance CTF based native tracer support.
RFC: https://www.mail-archive.com/dev@dpdk.org/msg154457.html
- Infrastructure to enable trace for dpdk library and applications
- UT and performance test cases for tracer
- Add trace points to ethdev, cryptodev, and eventdev library as a start.
# Introduce Graph subsystem for data/packet processing.
RFC: http://patches.dpdk.org/cover/65432/.
# Add basic packet processing nodes to work with the Graph subsystem.
# Example l3fwd-graph application to showcase the graph subsystem and basic packet processing nodes.
# v1 will be send based on TB and internal approvals. If there is no time then probably
postpone nodes and example application submission to v20.08.
Networking:
----------
# introduce IF proxy library
RFC: http://patches.dpdk.org/cover/64667/
# Add new rte_flow action to steer traffic to given PCIe device.
# Add l2fwd support for forwarding between asymmetric ports.
# octeontx2:
- Add rte_tm support.
- Add devargs for locking the NDC context for NIX and NPA.
# octeontx:
- Multi-segment support
- MTU
- Setting link up and down
- Rx/Tx HW offload checksum
- Flow control - pause frame
# Thunderx:
- Setting link up and down
Crypto:
------
# Event mode additions in ipsec-secgw
# octeontx2:
- Lookaside protocol support
- Crypto event adapter support
# Nitrox:
- Add 3DES_CBC, AES_CTR and AES_GCM symmetric crypto algorithms
Regexdev:
---------
# Complete the specification
# Review the common code from Mellanox when it is ready
# Add libpcre based SW driver.
next reply other threads:[~2020-02-27 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 7:49 Jerin Jacob Kollanukkaran [this message]
2020-03-29 21:31 ` Thomas Monjalon
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=BN8PR18MB24174D92B420FEFD5B228A17C8EB0@BN8PR18MB2417.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=GR-Ipbu-sw-dpdk@marvell.com \
--cc=anoobj@marvell.com \
--cc=arahman@marvell.com \
--cc=dev@dpdk.org \
--cc=dovrat@marvell.com \
--cc=jsrikanth@marvell.com \
--cc=pathreya@marvell.com \
--cc=pkapoor@marvell.com \
--cc=rmody@marvell.com \
--cc=rnagadheeraj@marvell.com \
--cc=shshaikh@marvell.com \
/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).