DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org, harini.ramakrishnan@microsoft.com
Cc: eilong@mellanox.com, pallavi.kadam@intel.com,
	ranjit.menon@intel.com, ocardona@microsoft.com,
	shshaikh@marvell.com, nareshkumar.pbs@broadcom.com,
	ravianan@cisco.com, talshn@mellanox.com, hgani@marvell.com,
	rksaripa@cisco.com, navasile@linux.microsoft.com,
	dmitry.kozliuk@gmail.com, dmitrym@microsoft.com,
	ophirmu@mellanox.com, thasreef@chelsio.com, tbashar@mellanox.com,
	fady@mellanox.com
Subject: [dpdk-web] [PATCH] update roadmap for Windows
Date: Wed, 29 Apr 2020 16:38:58 +0200	[thread overview]
Message-ID: <20200429143858.810497-1-thomas@monjalon.net> (raw)

Some tasks are not complete on time so the schedule is shifted,
and the deadlines are made a bit less agressive.

virt2phys kmod was added in early April to mitigate the lack
of netuio availability.

The new tracing framework could be ported on Windows.

Advanced memory management looks to be a fuzzy target,
waiting for progress in Microsoft.

No update on compiler bugs so far, just adding an email about TLS issue.

Broadcom, Chelsio, Cisco and Marvell are neither participating,
nor giving any update, so their PMD support is moved in "future".

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 content/roadmap/windows.md | 45 ++++++++++++++++++++++----------------
 1 file changed, 26 insertions(+), 19 deletions(-)

diff --git a/content/roadmap/windows.md b/content/roadmap/windows.md
index 868d63c..0d6c987 100644
--- a/content/roadmap/windows.md
+++ b/content/roadmap/windows.md
@@ -32,7 +32,7 @@ This list is obviously neither complete nor guaranteed.
 
 ✅ meson with clang + msvc linker: <https://github.com/mesonbuild/meson/pull/6483>
 
-- linking and performance of per-lcore variables with shared libraries
+- linking and performance of [per-core variables with shared libraries](//mails.dpdk.org/archives/dev/2020-February/157933.html)
 - structure alignment: <https://bugs.llvm.org/show_bug.cgi?id=24383>
 - AVX bug in gcc: <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412>
 
@@ -48,29 +48,32 @@ This list is obviously neither complete nor guaranteed.
 
 #### 2020-04-01
 
+✅ virt2phys kmod
+
+#### 2020-05-01
+
+- EAL log option
+- EAL timer
 - EAL basic memory management
 - PCI general probing
 - PCI bifurcated model
-- netuio source code hosting
-- netuio binary hosting
-- netuio documentation
-
-#### 2020-05-01
-
-- EAL advanced memory management
-- PCI netuio model
-- mempool
 - cmdline
 - Mellanox DevX library linkage
 
 #### 2020-06-01
 
+- tracing
+- mempool
 - mbuf
-- ethdev
+- netuio source code hosting
+- netuio binary hosting
+- netuio documentation
+- PCI netuio model
 - Mellanox glue layer
 
 #### 2020-07-01
 
+- ethdev
 - testpmd
 - ring PMD
 - pcap or other vdev PMD
@@ -79,28 +82,32 @@ This list is obviously neither complete nor guaranteed.
 
 #### 2020-08-01
 
-- Broadcom bnxt PMD Rx/Tx
-- Chelsio cxgbe PMD Rx/Tx
-- Cisco enic PMD Rx/Tx
 - Intel i40e PMD Rx/Tx
-- Marvell qede PMD Rx/Tx
 - Mellanox mlx5 PMD Rx/Tx
-- Mellanox documentation
 
 #### 2020-09-01
 
-- Mellanox rte_flow features
 - Functional tests in CI
+- Mellanox documentation
 
 #### 2020-10-01
 
-- only bug fixing after this point
+- PMD bug fixing after this point
 
 #### 2020-11-01
 
 - DPDK 20.11 LTS release
 
+#### 2020-12-01
+
+- Mellanox rte_flow features
+
 #### Future {#future}
 
-- Intel ice PMD
+- advanced memory management
 - multi-process support
+- Broadcom bnxt PMD
+- Chelsio cxgbe PMD
+- Cisco enic PMD
+- Intel ice PMD
+- Marvell qede PMD
-- 
2.26.0


                 reply	other threads:[~2020-04-29 14:39 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=20200429143858.810497-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=eilong@mellanox.com \
    --cc=fady@mellanox.com \
    --cc=harini.ramakrishnan@microsoft.com \
    --cc=hgani@marvell.com \
    --cc=nareshkumar.pbs@broadcom.com \
    --cc=navasile@linux.microsoft.com \
    --cc=ocardona@microsoft.com \
    --cc=ophirmu@mellanox.com \
    --cc=pallavi.kadam@intel.com \
    --cc=ranjit.menon@intel.com \
    --cc=ravianan@cisco.com \
    --cc=rksaripa@cisco.com \
    --cc=shshaikh@marvell.com \
    --cc=talshn@mellanox.com \
    --cc=tbashar@mellanox.com \
    --cc=thasreef@chelsio.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).