From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-web] [PATCH 3/3] update Broadcom roadmap for 20.08
Date: Mon, 8 Jun 2020 23:28:49 +0200 [thread overview]
Message-ID: <20200608212849.2886908-3-thomas@monjalon.net> (raw)
In-Reply-To: <20200608212849.2886908-1-thomas@monjalon.net>
Was announced in the dpdk-dev mailing list:
http://mails.dpdk.org/archives/dev/2020-June/169430.html
Reported-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/roadmap/_index.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 164f151..2d94cbf 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -18,6 +18,9 @@ This list is obviously neither complete nor guaranteed.
- Tx QoS marking API
- flow action object API
- flow sampling and mirroring API
+- bnxt VF representor and multi-device
+- bnxt optimization for Arm, burst mode info and flow counters
+- bnxt VLAN pop/push, VXLAN encap/decap, L2/L3/L4 rewrite and TTL decrement
- performance optimizations in mlx drivers for Arm platforms
- mlx5 memory management options, and queue stop/start
- mlx5 eCPRI matching and Tx scheduling for 5G
--
2.26.2
next prev parent reply other threads:[~2020-06-08 21:29 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 ` [dpdk-web] [EXT] " Jerin Kollanukkaran
2020-06-10 7:34 ` Thomas Monjalon
2020-06-08 21:28 ` Thomas Monjalon [this message]
2020-06-10 7:34 ` [dpdk-web] [PATCH 3/3] update Broadcom " 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=20200608212849.2886908-3-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--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).