DPDK website maintenance
 help / color / mirror / Atom feed
From: Jerin Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [EXT] [PATCH 2/3] update Marvell roadmap for 20.08
Date: Tue, 9 Jun 2020 04:04:52 +0000	[thread overview]
Message-ID: <BYAPR18MB24245FE4268AF5A58DA0CEACC8820@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20200608212849.2886908-2-thomas@monjalon.net>

Acked-by: Jerin Jacob <jerinj@marvell.com>

________________________________
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Tuesday, June 9, 2020 2:58 AM
To: web@dpdk.org <web@dpdk.org>
Cc: Jerin Kollanukkaran <jerinj@marvell.com>
Subject: [EXT] [PATCH 2/3] update Marvell roadmap for 20.08

External Email

----------------------------------------------------------------------
Was announced in the dpdk-dev mailing list:
https://urldefense.proofpoint.com/v2/url?u=http-3A__mails.dpdk.org_archives_dev_2020-2DMay_168992.html&d=DwIDAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=1DGob4H4rxz6H8uITozGOCa0s5f4wCNtTa4UUKvcsvI&m=VeJKcqcYYBtR34XQqiEaSTc_yT0BACPDsKRY2YA4gPM&s=BhCy69T1-SQlIHUmYdShBTlkWFqnZA3ngyVjvFiQAaw&e=

Reported-by: Jerin Jacob <jerinj@marvell.com>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 content/roadmap/_index.md | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 5b9e715..164f151 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -12,20 +12,29 @@ This list is obviously neither complete nor guaranteed.
 ### Version 20.08 (2020 August) {#2008}

 - external thread registration API
+- log registration constructor
+- removal of non-kernel based PCI probing
+- Arm CRC32 in generic API
+- Tx QoS marking API
 - flow action object API
 - flow sampling and mirroring API
 - performance optimizations in mlx drivers for Arm platforms
 - mlx5 memory management options, and queue stop/start
 - mlx5 eCPRI matching and Tx scheduling for 5G
 - mlx5 vDPA device counters
+- octeontx2 parameters for Rx/Tx context locking
+- octeontx2 packet mirroring
+- qede SR-IOV PF
 - vhost REPLY_ACK advertised unconditionally
 - vhost SET_STATUS
 - virtio-user GET/SET_PROTOCOL_FEATURES, REPLY_ACK, SET_STATUS
 - IF proxy
 - testpmd swap forwarding for L2/L3/L4
 - l2fwd forwarding between asymmetric ports
+- performance test for IP reassembly
 - performance test application for flow rules
-- octeontx2 crypto lookaside protocol and event adapter
+- octeontx2 crypto protocol lookaside and ChaCha-Poly
+- ipsec-secgw flow distribution and stats per-core
 - regexdev
 - regex driver based on libpcre
 - UBSan in build
--
2.26.2


  reply	other threads:[~2020-06-09  4:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 21:28 [dpdk-web] [PATCH 1/3] update Red Hat " Thomas Monjalon
2020-06-08 21:28 ` [dpdk-web] [PATCH 2/3] update Marvell " Thomas Monjalon
2020-06-09  4:04   ` Jerin Kollanukkaran [this message]
2020-06-10  7:34     ` [dpdk-web] [EXT] " Thomas Monjalon
2020-06-08 21:28 ` [dpdk-web] [PATCH 3/3] update Broadcom " Thomas Monjalon
2020-06-10  7:34   ` Thomas Monjalon
2020-06-09  9:54 ` [dpdk-web] [PATCH 1/3] update Red Hat " Maxime Coquelin
2020-06-10  7:34   ` 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=BYAPR18MB24245FE4268AF5A58DA0CEACC8820@BYAPR18MB2424.namprd18.prod.outlook.com \
    --to=jerinj@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).