From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
"fanzhang.oss@gmail.com" <fanzhang.oss@gmail.com>,
Akhil Goyal <gakhil@marvell.com>,
"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
Srikanth Yalavarthi <syalavarthi@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Volodymyr Fialko <vfialko@marvell.com>,
"cheng1.jiang@intel.com" <cheng1.jiang@intel.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Vamsi Krishna Attunuru <vattunuru@marvell.com>,
Amit Prakash Shukla <amitprakashs@marvell.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Rakesh Kudurumalla <rkudurumalla@marvell.com>,
"john.mcnamara@intel.com" <john.mcnamara@intel.com>,
Prasun Kapoor <pkapoor@marvell.com>,
Satananda Burla <sburla@marvell.com>,
Shivah Shankar Shankar Narayan Rao <sshankarnara@marvell.com>,
Derek Chickles <dchickles@marvell.com>
Subject: Marvell DPDK 23.11 Roadmap
Date: Tue, 1 Aug 2023 11:25:58 +0000 [thread overview]
Message-ID: <CO1PR18MB4796CFF4F90870EF7B86C92CC80AA@CO1PR18MB4796.namprd18.prod.outlook.com> (raw)
Marvell - DPDK v23.11 Roadmap for non-driver changes
===============================================
cryptodev
=========
1) Support for cryptodev to inject packets to ethdev Rx. On capable devices, this would help in using ethdev Rx offloads
(like inline reassembly, inner packet parsing) after cryptodev processing (like inbound IPsec).
dmadev
======
1) Support HW offload to free mbuf upon DMA transfer completion.
eventdev
========
1) Support dmadev adapter
http://patches.dpdk.org/project/dpdk/patch/20230724080744.1209290-1-amitprakashs@marvell.com/
2) Support mldev adapter
http://patches.dpdk.org/project/dpdk/patch/20230801070016.340-2-syalavarthi@marvell.com/
3)Introduce link profiles, a set of event queues can be grouped together as a profile and then
linked to an event port. The active profile can be switched before making a dequeue call.
mldev
=====
1) Update rte_ml_op structure, quantize/dequantize APIs to support rte_mbuf buffers.
2) Update rte_ml_model_info to support arbitrary shape input/output.
rte_security
============
1) Support TLS record processing offload
2) Introduce out of place support for inline ingress security sessions
https://patches.dpdk.org/project/dpdk/patch/20230309085645.1630826-1-ndabilpuram@marvell.com/
3) Hide structures ``rte_security_ops`` and ``rte_security_ctx`` as these are internal to DPDK library and drivers.
https://patches.dpdk.org/project/dpdk/patch/20230801081047.1219935-1-gakhil@marvell.com/
libpdcp
======
1) Support for handling Control PDU
Test applications
==============
1) test/crypto: add external mbuf test-case for look-aside IPsec
2) test/pdcp: add test cases to verify all packet lengths required to be supported with PDCP
3) test/dmadev: add test cases to verify rte_dmadev_copy_sg() functionality with all combinations of src & dst pointers.
4) app/test-dma-perf: DMA perf test application enhancement to support "device to memory" and "memory to device" data transfer and scatter-gather copy support.
4) app/graph: Add graph application for exercise different use-cases
Currently l3fwd-graph application demonstrates only l3fwd use case.
With this new application, a framework is provided to add new use cases
using static configuration file (.cli). Also a CLI framework to allow user
to configure some configuration at runtime
https://patches.dpdk.org/project/dpdk/patch/20230425131516.3308612-5-vattunuru@marvell.com/
Marvell - DPDK v23.11 Roadmap for driver changes
==========================================
cnxk-ethdev
===========
1) Support flow aging
2) Support port representor
cnxk-cryptodev:
==============
1) Support SM2 algorithm
mldev-cnxk
==========
1) Extend driver to support ML models compiled using TVM framework.
reply other threads:[~2023-08-01 11:26 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=CO1PR18MB4796CFF4F90870EF7B86C92CC80AA@CO1PR18MB4796.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=amitprakashs@marvell.com \
--cc=anoobj@marvell.com \
--cc=cheng1.jiang@intel.com \
--cc=dchickles@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=gakhil@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=pkapoor@marvell.com \
--cc=rkudurumalla@marvell.com \
--cc=sburla@marvell.com \
--cc=skori@marvell.com \
--cc=sshankarnara@marvell.com \
--cc=syalavarthi@marvell.com \
--cc=thomas@monjalon.net \
--cc=vattunuru@marvell.com \
--cc=vfialko@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).