From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Prasun Kapoor <pkapoor@marvell.com>,
Narayana Prasad Raju Athreya <pathreya@marvell.com>,
Ameen Rahman <arahman@marvell.com>
Subject: [dpdk-dev] 19.11 Marvell Roadmap
Date: Fri, 9 Aug 2019 05:55:07 +0000 [thread overview]
Message-ID: <BYAPR18MB24241701074EF907B47B5D1FC8D60@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
1) eBPF arm64 JIT support
2) Enhance UT cases for eBPF verification
3) Add new l2fwd-event eventdev application
4) Update l3fwd application to support event mode
5) Update ipsec-secgw application to support event mode
6) Add build infrastructure support for UBSan
7) ethdev enhancements
a) As a PMD optimization, introduce, an option do disable
rte_mbuf::packet_type, rte_mbuf::hash::rss and rte_mbuf::hash::fdir
field updates in Rx path if application wishes do so.
8) rte_flow enhancements
a) New patterns: NSH, IGMP, AH
b) New actions to support packet mirroring and multicast
9) Add KNI IOVA as VA support
10) Add OCTEON TX2 cryptodev PMD
11) Add OCTEON TX2 Inline IPsec support using rte_secuirty
12) Add OCTEON TX asymmetric crypto support
13) Add Nitrox Cryptodev PMD
14) OCTEON TX2 ethdev PMD enhancements
a) Implement item 6
b) Implement item 7
c) Add multicast filter support
d) TSO support
e) DSA/EDSA/eDSA parser
15) Fastlinq qede PMD enhancements
a) Add support to allow odd number of queues on 100G adapters
b) Add support for drop action in RTE_FLOW infrastructure.
c) Update base driver to use newer FW with latest fixes/enhancements
16) Bnx2x PMD enhancements
a) Update base driver to use latest mbox FW with fixes/enhancements
17) RegExdev RFC follow up
http://patches.dpdk.org/patch/55505/
next reply other threads:[~2019-08-09 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 5:55 Jerin Jacob Kollanukkaran [this message]
2019-08-15 9:29 ` 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=BYAPR18MB24241701074EF907B47B5D1FC8D60@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=arahman@marvell.com \
--cc=dev@dpdk.org \
--cc=pathreya@marvell.com \
--cc=pkapoor@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).