From: <jerinj@marvell.com>
To: <web@dpdk.org>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>, <ferruh.yigit@intel.com>,
<dovrat@marvell.com>, <sburla@marvell.com>,
<pathreya@marvell.com>, <anoobj@marvell.com>,
<irusskikh@marvell.com>, <pkapoor@marvell.com>,
"Jerin Jacob" <jerinj@marvell.com>
Subject: [dpdk-web] [dpdk-dev] [PATCH] update Marvell roadmap for 21.05
Date: Sat, 20 Feb 2021 14:16:38 +0530 [thread overview]
Message-ID: <20210220084638.2924944-1-jerinj@marvell.com> (raw)
From: Jerin Jacob <jerinj@marvell.com>
Signed-off-by: Jerin Jacob <jerinj@marvell.com>
---
content/roadmap/_index.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 6c51cb9..7d33e3b 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -25,6 +25,7 @@ This list is obviously neither complete nor guaranteed.
- octeontx2 mirroring
- qede initial support for next generation hardware
- qede flow API support
+- octeontx3 base driver for mempool, ethdev, eventdev and rte_flow support
<!-- Virtualisation -->
<!-- Network apps -->
- IF proxy
@@ -32,6 +33,10 @@ This list is obviously neither complete nor guaranteed.
<!-- Crypto -->
- IPv6 in lookaside IPsec example
- anti-replay in inline IPsec example
+<!-- Event -->
+- Introduce event vector support to reduce the scheduler overhead and to improve performance
+- Add support for event vector support in SW Rx eventdev Adapter
+- Update test-eventdev application to support event vector support
<!-- Compress -->
<!-- Others -->
- regex driver based on libpcre
--
2.29.2
next reply other threads:[~2021-02-20 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 8:46 jerinj [this message]
2021-02-28 17: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=20210220084638.2924944-1-jerinj@marvell.com \
--to=jerinj@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=dovrat@marvell.com \
--cc=ferruh.yigit@intel.com \
--cc=irusskikh@marvell.com \
--cc=pathreya@marvell.com \
--cc=pkapoor@marvell.com \
--cc=sburla@marvell.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/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).